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 562497 - Restore a file adds a readonly emblem to this file
Restore a file adds a readonly emblem to this file
Status: RESOLVED DUPLICATE of bug 555234
Product: nautilus
Classification: Core
Component: Trash
2.24.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-27 21:29 UTC by Jean-Philippe Fleury
Modified: 2008-11-29 12:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
Example before delete and after restoration (22.15 KB, image/png)
2008-11-27 21:42 UTC, Jean-Philippe Fleury
Details

Description Jean-Philippe Fleury 2008-11-27 21:29:08 UTC
Please describe the problem:
A restored file has always a readonly emblem added, whatever the permissions of the file.

Steps to reproduce:
1. Click right on a file and choose "Delete".
2. Open the trash.
3. Click right on the previous deleted file and choose "Restore".
4. Go to the folder that contains the restored file.

Actual results:
The file has a readonly emblem, whatever its permissions.

Expected results:
The file should have a readonly emblem if it's not readonly.

Does this happen every time?
Yes.

Other information:
Comment 1 Jean-Philippe Fleury 2008-11-27 21:42:46 UTC
Created attachment 123576 [details]
Example before delete and after restoration

It put a screen shot of a file in my desktop before the delete and after the restoration. In both situations, the permissions of the file are the same:

-rw-r--r--

and I'm the owner and the file is in my group.
Comment 2 Cosimo Cecchi 2008-11-29 12:06:30 UTC
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 555234 ***