FS#27726 - [gvfs] New filesystem upgrade breaks gvfs trash functionality
Attached to Project:
Arch Linux
Opened by Nathan Trapuzzano (nbtrap) - Monday, 26 December 2011, 19:37 GMT
Last edited by Allan McRae (Allan) - Saturday, 16 June 2012, 08:27 GMT
Opened by Nathan Trapuzzano (nbtrap) - Monday, 26 December 2011, 19:37 GMT
Last edited by Allan McRae (Allan) - Saturday, 16 June 2012, 08:27 GMT
|
Details
Description: It seems that the latest upgrade to
filesystem-2011.12-* has bro ken xdg trash functionality in
the following sense:
Files and folders in .Trash-* directories on external volumes are not being incorporated into trash:///. These files and folders simply do not appear in the trash mount, and one must delete the files manually in order to permanently remove them (instead of "Emptying Trash"). Steps to reproduce: 1. Mount an external volume with Thunar or pcmanfm (or perhaps any other file manager--I haven't tested every one). 2. Delete a file and/or folder on that volume with the gvfs-trash command (or equivalent, e.g. right-click > delete). 3. Note that the file/folder does not appear in trash:/// even though it appears in .Trash-*/files on the external volume. |
This task depends upon
- since filesystem-2011.12 /etc/mtab is a symlink to /proc/self/mounts.
Please report upstream about this issue asking to gain support for libmount. Don't forgot to paste the link so i can follow.
bugzilla.gnome.org, product gvfs
I'm curious, however: how do you know this is a gvfs bug? The last gvfs [stable] update was back on 2011-10-20, and my trash worked fine for weeks afterward, so I suspect upgrading a different package more recently broke gvfs in this regard, though I've had an impossible time figuring out exactly which package. I suspected it was the latest filesystem upgrade, but I can't be sure of that, becase removing /etc/mtab (and letting the file get auto-generated as it was before it was incorporated into filesystem-2011.12-*) did not fix the issue.
At any rate, this is very probably a gvfs bug.