https://bugs.kde.org/show_bug.cgi?id=445801
Antonio Rojas changed:
What|Removed |Added
Resolution|--- |DOWNSTREAM
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=445801
--- Comment #17 from Ahmad Samir ---
OK, thanks. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=445801
--- Comment #16 from Antonio Rojas ---
(In reply to Ahmad Samir from comment #15)
> If am reading this correctly, the issue is supposedly fixed by using
> pam_umask.so, which is probably what ArchLinux is already doing (but I don't
> know for sure).
https://bugs.kde.org/show_bug.cgi?id=445801
--- Comment #15 from Ahmad Samir ---
If am reading this correctly, the issue is supposedly fixed by using
pam_umask.so, which is probably what ArchLinux is already doing (but I don't
know for sure).
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=445801
--- Comment #14 from Vincent Minder ---
Thanks for the links. So for systemd the proper way to set umask would be
inside /etc/login.defs (always globally)?
I edited this file, but it didn't solve the issue on my Fedora system.
Even if it did, doesn't
https://bugs.kde.org/show_bug.cgi?id=445801
Ahmad Samir changed:
What|Removed |Added
Version|unspecified |5.23.4
CC|