Bug 129435 - No way to add a default entry for "Others" through the ACL directory permissions dialog.
Summary: No way to add a default entry for "Others" through the ACL directory permissi...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
: 150918 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-06-19 18:01 UTC by Zlamma
Modified: 2023-01-05 05:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zlamma 2006-06-19 18:01:22 UTC
Version:            (using KDE KDE 3.5.3)
Installed from:    Slackware Packages
OS:                Linux

Using a command line it is possible to add a default ACL entry to a directory issuing
setfacl -m d:o:rwx dirname
but such an option does not exist in the ACL file permissions dialog. It only has an option to set a default entry for named group or named user.
Comment 1 Thiago Macieira 2006-06-27 19:18:44 UTC
Till?
Comment 2 Zlamma 2006-06-27 19:52:37 UTC
Till? Guess you don't mean it's fixed?
Anyway try to be more verbose, even if i'm wrong, as I am a foreigner.

Just to clarify.
I was of course talking about the ACL directory permissions dialog, where only the default ACL attributes are available.
Sorry for that.
Comment 3 Pino Toscano 2007-10-17 12:04:33 UTC
*** Bug 150918 has been marked as a duplicate of this bug. ***
Comment 4 Zlamma 2007-10-17 13:23:58 UTC
If anyone needs clarifications, description of the duplicate http://bugs.kde.org/show_bug.cgi?id=150918 contains better explanations.
Comment 5 Andrew Crouthamel 2018-11-02 04:23:54 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-11-16 02:39:47 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 7 Justin Zobel 2022-12-06 00:56:49 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 8 Bug Janitor Service 2022-12-21 05:17:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2023-01-05 05:26:46 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!