Bug 480674

Summary:	File ~/.gtkrc-2.0 is created without conforming to umask settings
Product:	[Applications] systemsettings	Reporter:	0BADC0DE <vincenzo.romano>
Component:	kcm_style	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	mail, nate
Priority:	NOR
Version First Reported In:	5.27.10
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description 0BADC0DE 2024-02-01 12:48:42 UTC

SUMMARY
Everytime I login (via SDDM) I get a new  ~/.gtkrc-2.0 file created with file permissions not conforming to my umask settings  (currently it is 0077).


STEPS TO REPRODUCE
1.  Setup your umask policy, i.e. "umask 0077"
2.  Log out and then back in.
3. Execute "ls -l ~/.gtkrc-2.0"

OBSERVED RESULT
-rw-r--r-- 1 user user 265 2024-02-01 13:47:32+0100 /home/user/.gtkrc-2.0

EXPECTED RESULT
-rw------- 1 user user 265 2024-02-01 13:47:32+0100 /home/user/.gtkrc-2.0

SOFTWARE/OS VERSIONS
Kernel Version : 6.7.2.zen1-2
Plasma Version : 5.27.10-2
KDE Version : 23.08.4-1
Frameworks Version : 5.114.0-1
Qt5 Version : 5.15.12+kde+r10-1
Qt6 Version : 6.6.1-3
Wayland Version : 1.22.0-1
XOrg/Wayland Version : 23.2.4-2


ADDITIONAL INFORMATION

Comment 1 0BADC0DE 2024-03-29 07:34:29 UTC

I think I have got the issue to the core.
The entire KDE environment COULD NOT be started AFTER the user initialization script have been run.
In my case, it seems .bashrc is not read and thus no user-defined setting is run.
Since I have put the UMASK setting also inside /etc/login.defs this "bug" is not triggered any more.