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 562624 - [Nautilus] - "Apply permissions to enclosed files" won't set ownership permissions sub folders and files
[Nautilus] - "Apply permissions to enclosed files" won't set ownership permis...
Status: RESOLVED DUPLICATE of bug 371025
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.24.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-28 21:50 UTC by Ray
Modified: 2008-11-29 12:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Ray 2008-11-28 21:50:32 UTC
Please describe the problem:
"Apply Permissions to Enclosed Files" does not set owner to folders and files within a folder.

Steps to reproduce:
1. Choose a folder, right click, choose properties
2. Click on the permissions tab
3. Change Owner
4. Click the "Apply permissions to enclosed files"

Same results when using gksu nautilus


Actual results:
Only the owner of the folder selected changes.

Expected results:
All folders and files should have the same owner after pressing "Apply Permissions to Enclosed Files".

Does this happen every time?
This happens on every attempt.

Other information:
Comment 1 Cosimo Cecchi 2008-11-29 12:12:51 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 371025 ***
Comment 2 Ray 2008-11-29 12:47:37 UTC
The bug this is supposedly a duplicate of is over two years old, can you confirm that this is in fact a bug and not just a miss-understanding of the apply permissions feature. If this is in fact a bug then why hasn't it been fixed already?