https://bugs.kde.org/show_bug.cgi?id=395023
--- Comment #24 from [email protected] --- (In reply to Niklāvs Koļesņikovs from comment #23) > I can't be certain the issue I'm observing in KIO 6.19.0 is directly related > to the above mentioned MR or, if somehow this has been the case for a long > time and I only recently (possibly since update to 6.19.0?) hit this but > moving files to trash only works for one mount point of a btrfs filesystem > (seemingly whichever is first either in mounting order or lexical order but > unclear). > > Here's a reproducer for other mount points: > 1. In dolphin hit Ctrl+Shit+N and create a new folder here named `example` > 2. Since it should now be selected after creation, hit Del key to move it to > trash > 3. If the bug is triggered, the deletion will fail with a nonsensical error > that it could not be renamed and the following logged to terminal, where > dolphin was launched: kf.kio.workers.file: Could not rename file > "/home/user/folder/example" to "/home/user/.local/share/Trash/files/example" > [this is the same wrong location as mentioned previously in this bug] > 4. Even more surprisingly if you then close the error window and hit the Del > key a second time it will get moved to trash despite logging a second > identical message to terminal > > If this is not related to the MR in question or you'd like a new bug report > for this, let me know or feel free to just create one. I do not mind, if > someone else is credited for having reported this. TLDR: btrfs trash never worked right, if it worked it did only on the shortest mountpoint. This is because trash uses "solid" for enumerating devices where filesystems reside. In solid there can only be one filesystem per partition/volume and that can be mounted only to one place. for btrfs (or actually every mounted filesystem with multiple mountpoints) solid chooses the shortest mount path in the list of mountpoints per device. https://invent.kde.org/frameworks/kio/-/merge_requests/1983 does essentially blacklist solid if the filesystem is btrfs and use kmountpoint instead. Now that kmountpoint actually works with btrfs, this one could actually be updated and be merged, but I'm not sure if this would get accepted. Another thing I played was extending solid to somehow fake devices for every subvolume, but that is also not ideal. -- You are receiving this mail because: You are watching all bug changes.
