GNOME Bugzilla – Bug 332520
can't remove broken links from trash
Last modified: 2008-02-22 13:56:04 UTC
That bug has been described on https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/24540 "Using up to date breezy, I can't remove broken links from the trash. I have to do it from the command line. 1) make a broken link on your desktop. 2) click on it. 3) click "Move to trash" 4) open the trash icon 5) select the broken link, and press the delete key on the keyboard 6) asks if you want to remove file from trash. Click ok. Nothing happens. If I right click on the trash icon and select "Empty trash" it does work. (IE the link is succesfully removed)."
Other Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/35960 "To test this bug do these steps. 1) mkdir foo 2) ln -s foo bar 3) mv bar .Trash 4) rm foo 5) Go to .Trash with nautilus and try delete bar"
I can reproduce this with nautilus-2.14.1-1.fc5.1 under Fedora Core 5. Also, when I move a broken link to the trash and then select File > Empty Trash a weird dialog with the text "Error while deleting.", no title and buttons for "Cancel" and "Retry" appears. If I click Retry, the dialog just appears again; I have to click Cancel two times and then the file is deleted.
I also can reproduce this on SuSE Linux 10.1 (it comes with nautilus 2.12) Also, this doesn't just affect "Broken" symbolic links, but ANY AND ALL Symbolic Links. This is because "correct" symlinks link to relative targets, so unless the symlink is one directory below the home directory, the trash bin will not handle it correctly. Also, this applies to opening nautilus and right-clicking the symlink file and choosing 'Delete'. KDE doesn't have this problem, b.t.w. (I use both GNOME and KDE, prefer GNOME)
his bug is still present in ubuntu feisty, natuilus 2.18.1. When there is the broken link in the trash, selecting all the files in the trash and hitting del produces nothing but keeping selected only the broken link.
*** Bug 352600 has been marked as a duplicate of this bug. ***
This seems to have been fixed in the gio migration, works fine here with 2.21.91. Please reopen this bug or open a new one (under the GIO section) if you can reproduce this again with Nautilus >=2.21, thanks!