@Sebastien Bacher (@seb128) > @larson.erid.d: not sure it's really a "high-priority bug", such bind mount setups are not common. Could you tell us a bit more of cases where it's a concrete issue
Sure. This also happens on NFS mounts, which is more widespread than --bind. > and maybe read https://bugzilla.gnome.org/show_bug.cgi?id=604015 to see if you agree with what was said there? Would it solve the issue if nautilus was just directly deleting files on such locations? >From comments there I understand this happens on any filesystem where user has >permissions to create .Trash-* directory on the root, and which was not >mounted by gnome stuff (technically : those that >g_unix_mount_is_system_internal() returns FALSE for. This is approximately equal to "stuff mounted in /media/". ) Here's a summary of the problem : * On the one hand, nautilus happily moves files to mountpoint/.Trash* to put trashed files, on *any* filesystem (where .Trash* exists or nautilus has permissions to create it). * In the other hand, nautilus shows in trash:/// only *some* filesystems (depending on g_unix_mount_is_system_internal). So, there no doubt that: * https://bugzilla.gnome.org/show_bug.cgi?id=604015 is the correct upstream bug. * Nautilus is inconsistent. * trash-cli shows that a consistent behavior is possible >From upstream: > The trash backend currently only tracks trashed files on "user interesting" > mounts -- those that g_unix_mount_is_system_internal() returns FALSE for. > This > is approximately equal to "stuff mounted in /media/". > It is certainly a bug, however, that nautilus (via g_file_trash()) and the > trash backend disagree on which volumes ought to be supported. Anyone to offer a patch to upstream ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/594674 Title: Trash is not shown on --bind mounted filesystems Status in The "G" Library - GLib: Confirmed Status in Nautilus: Invalid Status in “glib2.0” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Bug description: Binary package hint: nautilus I have a secondary partition, mounted at /media/data, from which I --bind mount a directory to be my ~/Videos using fstab. When I use Nautilus to navigate into ~/Videos and move a file into trash (either using Delete or by dragging or whatever), the file vanishes, but does not show up when I open Trash from the side panel. If I press Ctrl+H to see hidden files I find a ~/Videos/.Trash-1000 directory, under which the file has been moved. Navigating to /media/data/path/Videos and removing the file from there moves it under /media/data/.Trash-1000, from where it correctly shows up in the trash can. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Tue Jun 15 19:03:29 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/594674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
