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 568608 - Can't completely empty trash containing read-only folders.
Can't completely empty trash containing read-only folders.
Status: RESOLVED DUPLICATE of bug 404600
Product: nautilus
Classification: Core
Component: Trash
2.24.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-21 21:09 UTC by Credomane
Modified: 2009-01-22 14:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Credomane 2009-01-21 21:09:44 UTC 
Please describe the problem:
Emptying the trash with a read-only folder. That folder along with all sub-folders and files silently fail to delete. While all writable folders will be deleted correctly. Read-only files will delete properly unless they are in a read-only folder of course.

Folders cannot be made writable inside of trash through the GUI because nautilus returns, "Action not supported by backend." Folder must be moved out of the trash then made writable and back in. Then the folder will finally be properly removed when emptying the trash.

Steps to reproduce:
1. Create a folder.
2. Make said folder read-only.
3. Move it to the trash.
4. Empty Trash.


Actual results:
The folder is still there.

Expected results:
The trash to be empty.

Does this happen every time?
Yep.

Other information:
Comment 1 Cosimo Cecchi 2009-01-22 10:12:37 UTC 
This should have been fixed with the new trash backend in GVfs.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 404600 ***
Comment 2 Credomane 2009-01-22 14:23:29 UTC 
Figured there would be a bug already but I couldn't find it. Seems I was looking in the wrong place. Sorry about that and thanks to Ryan Lortie for fixing it.

Though I didn't have this problem with the old '~/.Trash/' folder style as the bug report shows. Only the new one located at '~/.local/share/Trash/'

Oh well fixed is fixed.