← Back to team overview

desktop-packages team mailing list archive

[Bug 594674] Re: Trash is not shown on --bind mounted filesystems


Ubuntu 14.04

This problem occurs too in symlink folders on another drive:

I have created several symlinks in my home folder to folders in another drive.
I have changed the permissions of that mounted drive:

    drwxrwxrwx   6 root  root  4,0K oct 13 17:30 media/

When I delete some file/folder on some of that symlinks, from Nautilus,
it's sent to Trash folder in `media` drive:

    $ ll /media/.Trash-1000/
    total 8,0K
    drwx------ 2 simon simon 4,0K oct 13 17:32 files/
    drwx------ 2 simon simon 4,0K oct 13 17:32 info/

but it isn't showed in Nautilus trash.

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.

  Trash is not shown on --bind mounted filesystems

Status in The "G" Library - GLib:
Status in Nautilus:
Status in “glib2.0” package in Ubuntu:
Status in “nautilus” package in Ubuntu:

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
  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)
  SourcePackage: nautilus

To manage notifications about this bug go to: