After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 776262 - Nautilus doesn't see items in local USB Trash
Nautilus doesn't see items in local USB Trash
Status: RESOLVED DUPLICATE of bug 662946
Product: glib
Classification: Platform
Component: gio
2.50.x
Other Linux
: Normal major
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2016-12-19 11:16 UTC by Inactive account
Modified: 2016-12-19 13:17 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22



Description Inactive account 2016-12-19 11:16:46 UTC
I have found that after upgrading from Ubuntu GNOME 16.04.1 with GNOME 3.20 to Ubuntu GNOME 16.10 with GNOME 3.22 that if I go into a USB and click the Nautilus button to "Move to Wastebasket" that it doesn't actually appear in my Wastebasket. If I then click the Undo button that comes up with the notification of the action in Nautilus, nothing happens. This is a before and after from the tree -a command:

Before:

    /media/<username>/<usb-name>/
    ├── 123
    │   ├── IMAG4613.jpg
    │   └── IMAG4617.jpg
    └── .Trash-1000
        ├── files
        └── info

    4 directories, 2 files

After:

    /media/<username>/<usb-name>/
    └── .Trash-1000
        ├── files
        │   └── 123
        │   ├── IMAG4613.jpg
        │   └── IMAG4617.jpg
        └── info
            └── 123.trashinfo

    4 directories, 3 files

This is the case with all my USBs, but what is interesting is that I tried using Dolphin instead of Nautilus to bin the files and it worked using Dolphin, but I believe only because it moved it to
the Trash of the actual system, rather than using the Trash system local to the USB.

But this has become rather annoying to me as I can no longer delete files on USBs unless I enable the immediate permanent removal button or cut and copy them over to my system to deal with them there.

I originally reported this issue here: https://bugs.launchpad.net/ubuntu-gnome/+bug/1651086 But thought I should also do so upstream.
Comment 1 Ondrej Holy 2016-12-19 12:09:49 UTC
Thanks for your bug report. I suppose it is a duplicate of the Bug 662946, which should be already fixed in GLib 2.50.1. What glib version do you have?
Comment 2 Jeremy Bicha 2016-12-19 12:31:57 UTC
Ondrej, I'm not the original bug reporter but yes, it does sound like it's a duplicate of that bug. GLib 2.50.1 is currently a proposed update for Ubuntu 16.10. Once it's verified, it will be pushed to all Ubuntu 16.10 users.
Comment 3 Ondrej Holy 2016-12-19 13:17:01 UTC
Ok, thanks, let's mark this as a duplicate then. If you see this issue also with GLib 2.50.1, please let us know...

(So, something like the following should fix your issue: "sudo apt-get install glib/yakkety-proposed")

*** This bug has been marked as a duplicate of bug 662946 ***