[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2026-02-04 Thread Jerry Quinn
https://bugs.kde.org/show_bug.cgi?id=395023

Jerry Quinn  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #26 from Jerry Quinn  ---
This bug still affects me on Ubuntu 24.04 with a btrfs non-home filesystem, not
involving sub-volumes.  I've created an ubuntu bug there:
https://bugs.launchpad.net/ubuntu/+source/kio/+bug/2140486

As others have, I've confirmed that trash-cli works fine for this use case.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2026-01-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #25 from [email protected] ---
I have btrfs on a secondary disk and used to have this problem, but right now
it's working. Deleted files go correctly to the trash on the appropriate disk,
and .Trash-$UID is created if it doesn't exist.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2026-01-10 Thread RM
https://bugs.kde.org/show_bug.cgi?id=395023

RM  changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-12-27 Thread Thomas H.
https://bugs.kde.org/show_bug.cgi?id=395023

Thomas H.  changed:

   What|Removed |Added

 CC||commander.sirow+kde@googlem
   ||ail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-12-24 Thread pallaswept
https://bugs.kde.org/show_bug.cgi?id=395023

pallaswept  changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-11-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-10-18 Thread Niklāvs Koļesņikovs
https://bugs.kde.org/show_bug.cgi?id=395023

Niklāvs Koļesņikovs <[email protected]> changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #23 from Niklāvs Koļesņikovs <[email protected]> ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-10-18 Thread bugzilla_noreply
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.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-10-18 Thread Antti Savolainen
https://bugs.kde.org/show_bug.cgi?id=395023

Antti Savolainen  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #20 from Antti Savolainen  ---
*** Bug 508514 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-10-18 Thread Antti Savolainen
https://bugs.kde.org/show_bug.cgi?id=395023

Antti Savolainen  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #21 from Antti Savolainen  ---
*** Bug 452074 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-10-03 Thread Milan Hauth
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #22 from Milan Hauth  ---
in Bug 508514
the source filesystem is ZFS mounted on /media/somelabel
and the destination filesystem is EXT4 mounted on /
(so not only the BTRFS filesystem is affected)

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-09-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #19 from [email protected] ---
(In reply to Bug Janitor Service from comment #15)
> A possibly relevant merge request was started @
> https://invent.kde.org/frameworks/kio/-/merge_requests/1537

The base for the (closed) MR is now
https://invent.kde.org/frameworks/kio/-/merge_requests/1983
https://invent.kde.org/frameworks/kio/-/merge_requests/1537 could actually
already work, but without
https://invent.kde.org/frameworks/kio/-/merge_requests/1983 "implicit"[1]
subvolumes break things (as they do already, just look at the properties dialog
in dolphin).

If https://invent.kde.org/frameworks/kio/-/merge_requests/1537 would get
merged, the trash resides on the explicit mounted subvolume root (again, it is
only feasable to use the information in /proc/self/mountinfo, there is no api
to get every subvolume on a btrfs filesystem, you can only check if a file is
on the same or different subvolume)

[1] the subvolumes that do not show up in /proc/self/mountinfo.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-09-07 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #18 from [email protected] ---
How is the progress one year on?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2025-01-25 Thread Kuro
https://bugs.kde.org/show_bug.cgi?id=395023

Kuro  changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-12-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||orhgyvqb82st0lgpsj9m@kill-t
   ||he-newsletter.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-12-02 Thread Andy Hall
https://bugs.kde.org/show_bug.cgi?id=395023

Andy Hall  changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-11-22 Thread Synthetic451
https://bugs.kde.org/show_bug.cgi?id=395023

Synthetic451  changed:

   What|Removed |Added

 CC||bugs.kde.org.facelift226@pa
   ||ssmail.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-09-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-09-08 Thread Antti Savolainen
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #17 from Antti Savolainen  ---
There are a couple of workarounds. You can use trash-cli, althought full
compatibility with the dolphin trash menu item is not guaranteed, or you can
press shift+delete to delete the files on the spot without moving them to the
trash first.

I'm personally slowly moving to bcachefs on my storage drives. It supports RAID
for non-uniform drives and has compression.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-09-08 Thread calvin
https://bugs.kde.org/show_bug.cgi?id=395023

calvin  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #16 from calvin  ---
MR to fix this appears to be dead, any good workarounds for mounting a
secondary hard drive to avoid trashing moving files to the ssd? The custom
desktop entry works ok but you can't bind the delete key to it without some
jank. I'd even take running a new filesystem if it has good compression
support.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-08-20 Thread smow
https://bugs.kde.org/show_bug.cgi?id=395023

smow  changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-06-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-01-27 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-01-13 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=395023

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #15 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/frameworks/kio/-/merge_requests/1537

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-01-08 Thread Antti Savolainen
https://bugs.kde.org/show_bug.cgi?id=395023

Antti Savolainen  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #14 from Antti Savolainen  ---
*** Bug 479525 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2024-01-02 Thread Pedro V
https://bugs.kde.org/show_bug.cgi?id=395023

Pedro V  changed:

   What|Removed |Added

 CC||voidpointertonull+bugskdeor
   ||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-11-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #13 from [email protected] ---
*** Bug 474680 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-11-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #12 from [email protected] ---
To really fix this I need some help from the kde team deciding if/how solid
should be changed...
Solid Frameworks has also wrong assumptions about btrfs.
looking at
https://invent.kde.org/frameworks/solid/-/blob/master/src/solid/devices/backends/udisks2/udisksstorageaccess.cpp?ref_type=heads
baseMountPoint looks for the (first) mountpoint that has its root in /.
This is a wrong assumption with btrfs in multiple ways: first there might be
multiple filesystem roots mounted from the same device, second the "root" of
the filesystem does not need to be mounted (actually on my system it is not)

second even tough udiskctl lists every mountpoint of a filesystem/device, solid
only filters the btrfs root "/", if there are multiple and "/" is not mounted,
then the first.

the MR for KMountPoint will fix this issue partially but create another (minor)
one: for every subvolume a .Trash directory will be created but it will be only
used if it matches with solid's view.
This could be fixed by a second MR that changes kio trash that is checks if
solid mount and kmountpoint match. if not than no trash directory should be
created.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-11-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #11 from [email protected] ---
(In reply to mike from comment #10)
> wow, the bug kio not handling btrfs is old..
> The only thing that made me notice that a kdevelop crash triggered by a new
> method isOnCifs that could not handle "not found" mountpoints, the very same
> root cause of this issue..
> 
> anyhow https://invent.kde.org/frameworks/kio/-/merge_requests/1422 would
> implement btrfs handling:
> "subvolume-less" roots and explicitly mounted subvolumes are straight
> forward.
> What I also do is search for implicitly mounted subvolume "roots" and return
> that as mountpoint, so cross mountpoint moves should not occur

I have good and bad news for you:
with the MR above the .Trash-$UID directory is created (if permissions allow of
course).
It seems that when the file is moved to the trash the solid framework is used
to find the "storage media". That has no idea what to do with subvolumes of any
kind. It would be probably possible for solid to find every explicitly mounted
subvolume, but enumerating every subvolume is simply not possible, so this will
never fully work is the "move to trash" is based on solid.

The simplest case (external btrfs, only one subvolume mounted) works. Put
simply: if you see a drive icon in dolpin, exactly that subvolume will work,
every other will land in .local/share... even though the .Trash-$UID
directories are created

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-11-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #10 from [email protected] ---
wow, the bug kio not handling btrfs is old..
The only thing that made me notice that a kdevelop crash triggered by a new
method isOnCifs that could not handle "not found" mountpoints, the very same
root cause of this issue..

anyhow https://invent.kde.org/frameworks/kio/-/merge_requests/1422 would
implement btrfs handling:
"subvolume-less" roots and explicitly mounted subvolumes are straight forward.
What I also do is search for implicitly mounted subvolume "roots" and return
that as mountpoint, so cross mountpoint moves should not occur

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

   Assignee|[email protected]   |[email protected]

--- Comment #9 from [email protected] ---
Unassigned myself because I just realized Michael Saxl is already working on
this: https://invent.kde.org/frameworks/kio/-/merge_requests/1422

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-10-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #8 from [email protected] ---
Did some debugging, and it turns out the issue is rather complicated.

The current code checks for the mount point of a path using two conditions
(https://invent.kde.org/frameworks/kio/-/blob/c43c6a06d25d8281bc898eb0ba3032840bf9d53b/src/core/kmountpoint.cpp#L442)
1. The device id of the mount point (as reported in /proc/self/mountinfo) needs
to match the device id of the path
2. The path needs to start with the path of the mount point.

However, for btrfs, the device id of the mount point reported by stat and in
mountinfo are different (see references).

In my view, this leaves us with the following options:
1. Resolve this as WON'T FIX
2. Revert to the old behavior of not using device id, and only using the
longest matching prefix to find the mount point of a path.
(https://invent.kde.org/frameworks/kio/-/merge_requests/503)
3. Find some other way to find the mount point of a path.

Would other developers/contributors be able to comment on this?

Thanks!

References:
https://bugzilla.redhat.com/show_bug.cgi?id=711881
https://stackoverflow.com/questions/39494077/linux-stat2-call-gives-non-existing-device-id
https://linux-btrfs.vger.kernel.narkive.com/AXOOKc9G/why-does-stat-return-invalid-st-dev-field-for-btrfs

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-10-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #7 from [email protected] ---
I plan to work on this, if nobody else is working on it.
But nothing quick promised (probably will take a few weeks).

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-10-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

   Assignee|[email protected]   |[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-10-26 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=395023

David Faure  changed:

   What|Removed |Added

   Assignee|[email protected]   |[email protected]

--- Comment #6 from David Faure  ---
Given that I don't care about btrfs, let me un-assign this bug from myself to
avoid any false hopes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-10-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-10-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-09-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=395023

[email protected] changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-08-03 Thread Oleg Grigorev
https://bugs.kde.org/show_bug.cgi?id=395023

Oleg Grigorev  changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-08-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=395023

Nate Graham  changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-08-03 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=395023

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=76380

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2023-01-21 Thread Eridani Rodríguez
https://bugs.kde.org/show_bug.cgi?id=395023

Eridani Rodríguez  changed:

   What|Removed |Added

 CC||[email protected]

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2022-12-10 Thread Graham Perrin
https://bugs.kde.org/show_bug.cgi?id=395023

Graham Perrin  changed:

   What|Removed |Added

 CC||[email protected]
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=357041

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2022-11-14 Thread Schlaefer
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #5 from Schlaefer  ---
trash-cli [1] handles it correctly btw.

So if you're affected, install trash-cli, create e.g.
~/.local/share/kservices5/ServiceMenus/moveToTrash.desktop with:

---

[Desktop Entry]
Name=Move To Trash
Type=Service
MimeType=all/all;
ServiceTypes=KonqPopupMenu/Plugin
Actions=moveToTrash
X-KDE-Priority=TopLevel

[Desktop Action moveToTrash]
Name=Move To Trash
Icon=org.kde.plasma.trash
Exec=trash %U

---

creates a new "Move to Trash" context menu item that offers a workaround until
this gets resolved.

[1] https://github.com/andreafrancia/trash-cli

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2022-05-18 Thread Emanuele
https://bugs.kde.org/show_bug.cgi?id=395023

Emanuele  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #4 from Emanuele  ---
I confirm on filesystem Btrfs, also reproduced on a filesystem FAT, is it
expected?

Test: Virt-Manager
OS:   Fedora 36
Dolphin 21.12.2
KDE Frameworks 5.91.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2022-05-16 Thread Francesco
https://bugs.kde.org/show_bug.cgi?id=395023

Francesco  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #3 from Francesco  ---
I can confirm the same exact issue, verified today on this two systems:

(my main laptop)
Operating System: Arch Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3630QM CPU @ 2.40GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000

(testing virtual machine)
Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-3630QM CPU @ 2.40GHz
Memory: 3.8 GiB of RAM
Graphics Processor: SVGA3D; build: RELEASE; LLVM;


I verified it either on external btrfs volume connected via usb or an image
file with btrfs on it. When I delete a file this is moved to
~/.local/share/Trash instead to .Trash-1000 on the original btrfs volume.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2021-12-11 Thread Schlaefer
https://bugs.kde.org/show_bug.cgi?id=395023

Schlaefer  changed:

   What|Removed |Added

 CC||[email protected]

--- Comment #2 from Schlaefer  ---
Created attachment 16
  --> https://bugs.kde.org/attachment.cgi?id=16&action=edit
Example Dolphin trash ext4 and btrfs

This is also not limited to subvolumes of the same root, but happens between
different mediums too. The attachment shows two external media, one ext4
(external trash is used) and the other one btrfs (file is copied to the
internal trash).

Dolphin Version 21.12.0
Operating System: EndeavourOS
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.7-zen1-1-zen (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2020-03-28 Thread Johannes Pfrang
https://bugs.kde.org/show_bug.cgi?id=395023

Johannes Pfrang  changed:

   What|Removed |Added

 CC||[email protected]
   ||m

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes

2018-06-04 Thread Thomas H .
https://bugs.kde.org/show_bug.cgi?id=395023

--- Comment #1 from Thomas H.  ---
Might also be related to this issue:
https://bugs.kde.org/show_bug.cgi?id=248222

-- 
You are receiving this mail because:
You are watching all bug changes.