Hide Forgot
Description of problem: Nautilus allows moving files to Trash on removable drives, but the "Empty Trash" action never becomes visible. .Trash-<UID> folder is created successfully and the files are moved there, but they do not show up in the special Trash folder in Nautilus either. I have tried this at least on two thumb drives and a memory card reader. It is fairly annoying to open the terminal just to "rm -rf" the trash and free up the space. Version-Release number of selected component (if applicable): nautilus-3.0.2-1.fc15.x86_64.rpm How reproducible: Always Steps to Reproduce: 1. Insert a removable drive (2. Delete the .Trash-folder(s) on the drive if any) 3. Copy or create a file on the drive 4. Move the file to Trash Actual results: The deleted file does not show up in the Trash and the Trash is not emptyable. .Trash-<UID> folder is created and the file is there. Expected results: The deleted file should show up in the Trash and the Trash should be emptyable.
Actually, this might be a dupe of: https://bugzilla.redhat.com/show_bug.cgi?id=708889 and/or https://bugzilla.redhat.com/show_bug.cgi?id=699800
I can confirm that this bug is still present in Fedora 16 nautilus-3.2.1-2.fc16.x86_64. But if you start desktop in forced legacy mode you'll see deleted file in trash and you'll be able to empty trash, so this problem depends on gnome-shell. I tried to reproduce this problem in Linux Mint 12 in gnome-shell mode but everything works as expected there.
I am still seeing this behaviour in gnome , without gnome-shell, and my setup is : Installed Packages nautilus.i686 3.2.1-2.fc16 @fedora nautilus-actions.i686 3.1.3-1.fc16 @fedora nautilus-actions-docs.noarch 3.1.3-1.fc16 @fedora nautilus-dropbox.i386 0.7.1-1.fc10 @Dropbox nautilus-extensions.i686 3.2.1-2.fc16 @fedora nautilus-image-converter.i686 0.3.1-0.1.git430afce31.fc15 @fedora nautilus-open-terminal.i686 0.19-2.fc16 @fedora nautilus-pastebin.i686 0.5.0-5.fc15 @fedora nautilus-phatch.noarch 0.2.7-7.fc16 @fedora nautilus-python.i686 1.0-1.fc16 @fedora nautilus-search-tool.i686 0.3.0-10.fc15 @fedora nautilus-sendto.i686 1:3.0.1-1.fc16 @fedora nautilus-sound-converter.i686 3.0.1-2.fc16 @fedora I have tested it on FAT32 external usb drive and an ext4 external usb drive. 1. Delete a file on the external drive 2. Open the trash folder Result: No file is shown in the trash, but the file can be found in .Trash-xxx
I can confirm that this bug. nautilus-3.2.1-2.fc16.i686 gnome-shell-3.2.1-2.fc16.i686
For me fixed in Fedora 17
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.