Am Montag, 27. Dezember 2021, 17:01:00 CET schrieb Neal Gompa:
> On Mon, Dec 27, 2021 at 10:17 AM Emmett Culley
> <lst_manage@xxxxxxxxxxxxxxx> wrote:
>
> >
> >
> > I first discovered this issue when a user complained she could not access
> > a file I created on an NFS4 share.
>
> >
> >
> > I don't see this issue if I use fish:// to access any directory, local or
> > remote.
>
> >
> >
> > We are on fully updated KDE fedora 34 and 35 systems, and this has been a
> > problem for quite awhile, through many Fedora updates, possibly as far
> > back as fedora 18 (arbitrary number). Until now I've usually just run
> > chmod -R g+w on the share on the file server or locally when it matters,
> > then went about my business. I have put it off too long and so did a bit
> > of investigation.
>
> >
> >
> > This happens every time on both Konqueror and Dolphin. It never happens
> > in Konsole. Meaning that if I open Konsole and cd to /fs1/work (the nfs
> > share), and create a file or directory, the permissions are set to 664
> > and 2775 (SGID is set for all directories) as expected, with a umask of
> > 002 for all users. Note that the umask on both servers and clients are
> > set to 002.
>
> >
> >
> > So only Dolphin and Konqueror ignore the umask=0002 setting, and only when
> > not accessing a file system via fish. This happen on both remote NFS
> > shares and locally.
Ah, I don't think that is a bug. I had the same issue, but not only for dolphin, but all KDE apps (like kid3 etc.). So I stressed google up an down and finally found the reason for it: KDE is started since some fedora versions via systemd --user part. And this systemd does not inherit parents umasks but sets it to 0022 by default - unless it is told to do otherwise. This can be done in the systemd units via UMask setting or via pam_umask in the pam config files.
simple add "session optional pam_umask.so usergroups" to the /etc/pam.d/system-auth file, reboot and login again - and dolphin should create files as requested (at least id did for me during some short tests).
Regards
Martin
>
> >
>
>
> Please file a bug upstream at bugs.kde.org. Upstream KDE developers
> look there for these things and will be able to do something about the
> problem.
>
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> _______________________________________________
> kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List
> Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List
> Archives:
> https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
_______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
