Bug 200644 - When changing only GID of a folder, in all subfolders and files, permission are set, too.
When changing only GID of a folder, in all subfolders and files, permission a...
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: kdebase (Show other bugs)
5
All Linux
medium Severity high
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-29 13:17 EDT by Klaus Munsteiner
Modified: 2008-01-23 05:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-23 05:00:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Picture of step 3 to reproduce (131.23 KB, image/png)
2006-07-29 13:17 EDT, Klaus Munsteiner
no flags Details

  None (edit)
Description Klaus Munsteiner 2006-07-29 13:17:14 EDT
Description of problem:
When changing ONLY the ownership of the group and set checkbox "Apply all
changes to their subfolders and their contents" all access permissions in all
subdirectories an files are changed, too. 

Version-Release number of selected component (if applicable):
Konqueror 3.3.5-0.4.fc5

How reproducible:

Steps to Reproduce:
1. Copy any directory for testing.
2. Change only the group and set checkbox "Apply all changes to their subfolders
and their contents"
3. All access permissions in the subdirectories and files are set to the values
of the directory you started the change.
  
Actual results:
Access permissions of all subdirectories and files are changed, too.

Expected results:
ONLY group should be changed, NO access permissions

Additional info:
I testet this on a P4 and Athlon64 (x86_64)
Comment 1 Klaus Munsteiner 2006-07-29 13:17:15 EDT
Created attachment 133283 [details]
Picture of step 3 to reproduce
Comment 2 Lukáš Tinkl 2008-01-23 05:00:26 EST
Fixed upstream (tested against KDE 3.5.8)

Note You need to log in before you can comment on or make changes to this bug.