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 378615 - No notification if emptying trash fails
No notification if emptying trash fails
Status: RESOLVED DUPLICATE of bug 339596
Product: nautilus
Classification: Core
Component: Trash
2.16.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-23 20:56 UTC by Duncan Lithgow
Modified: 2007-03-08 20:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Duncan Lithgow 2006-11-23 20:56:00 UTC
Sometimes trash includes files the user can't delete. For example some files which where put there working as sudo root. If I right click the trash icon and select 'Empty trash' it appears to do what I've asked for. The only way I could tell that it hadn't worked was by noticing that the icon still shows trash - normally thought once I've told it to empty I don't think about it any more.

Other information:
Comment 1 Christian Kirbach 2007-01-19 23:32:35 UTC
Hmm doesn't it tell you that it encountered files it cannot delete? at least it does this for me -- Bug 354394 – Undeletable files and folders allowed into the bin
Comment 2 Duncan Lithgow 2007-01-21 11:56:20 UTC
No, it didn't tell me anything. It just deleted what it could and silently skipped what it couldn't delete.

Just now I'm unsure how to recreate this bug, what's a good way of trying to put an undeletable file in trash.
Comment 3 Christian Kirbach 2007-01-25 23:04:48 UTC
For GNome 2.16 and 2.17, I get a warning that it cannot delete some files

to reproduce see Bug 354394

"Basically, files and folders with wrong permissions may end up in the bin. When
purging the bin this fails because of missing permissions to erase the items of
question:

* (sub)folders or files (in subfolders) that the user lacks write permissions
for
* (sub)folders or files (in subfolders) that belong to other users"
Comment 4 Duncan Lithgow 2007-03-08 20:36:00 UTC

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