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 523358 - Nautilus does not warn when deleting read-only files
Nautilus does not warn when deleting read-only files
Status: RESOLVED DUPLICATE of bug 486780
Product: nautilus
Classification: Core
Component: Trash
2.22.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-19 13:21 UTC by Mathias Menzer
Modified: 2008-03-19 17:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Mathias Menzer 2008-03-19 13:21:03 UTC
Please describe the problem:
Nautilus deletes files without warning even when they have been marked read-only (444) or don't read (000). You have to be the owner of the file to do this. The behavior when using 'rm' on the console is a warning that the file is write protected. This should be implemented in Nautilus since at the moment no effective protection against accidental removal of files is possible.

Steps to reproduce:
1. Create a new file
2. Change its permissions to read-only for you, group and others
3. Trash and delete it with Nautilus

Actual results:
There is now warning or error message

Expected results:
A warning should appear, as when using 'rm'; "You are about to delete files which have been write-protected. Proceed Yes/No"

Does this happen every time?
Yes

Other information:
Bug in Nautilus 2.20.x: http://bugzilla.gnome.org/show_bug.cgi?id=486780
Comment 1 Cosimo Cecchi 2008-03-19 17:36:06 UTC
Hi Mathias, please do not file duplicate bugs...I see that you already commented on another report, which you seem to have copied and pasted in another one.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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