Bug 155018

Summary:	Changes on POSIX ACL are not applied
Product:	[Frameworks and Libraries] kdelibs	Reporter:	Luigi Toscano <luigi.toscano>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	faure, kde, markus
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Luigi Toscano 2008-01-03 13:33:53 UTC

Version:            (using KDE Devel)
Installed from:    Compiled sources

If you try to modify the POSIX ACLs for a file, the new settings are not applied.

I think that the problem lies on the communication of the metadata between the KPropertiesDialog (KFilePermissionsPropsPlugin::applyChanges) and the invoked ChmodJob, but I was not able to find the source of the issue.

Comment 1 David Faure 2008-01-17 18:39:17 UTC

Note: kde4 regression.

Comment 2 David Faure 2008-10-04 02:28:19 UTC

Seems to work here, except that reopening the properties dialog doesn't show the updated permissions (I'm looking into that bug). But if I press F5 in the view then the properties dialog shows the correct ACLs. Can you confirm that?

Comment 3 Luigi Toscano 2008-10-29 18:29:13 UTC

Sorry for the delayed response.

Yes, I can confirm the described behaviour both on current trunk and the 4.1.x branch.
Moreover, when you reopen the properties dialog immediatly after making changes, the "access permission" pane shows the correct informations (i.e. when a new ACL is added, the three comboboxes are greyed out even if the "advanced permission" dialog does not show the changes).

Comment 4 Markus Brueffer 2009-12-28 23:46:59 UTC

I can confirm that this is still a problem with KDE 4.3.4.

Comment 5 Janek Bevendorff 2012-09-07 13:53:19 UTC

Marking this as a duplicate of the (newer) bug 299155 since that one is shorter and more precise for the problems left in recent KDE version.
Changes to the default ACLs for user, group and others seem to be applied here (KDE 4.9.1), but the problem described in Comment #3 is still there.

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