Bug 185407

Summary: No warning when systemsettings can't write config files
Product: [Applications] systemsettings Reporter: Markus Strobl <mstrobl2>
Component: generalAssignee: System Settings Bugs <sourtooth+ssbugs>
Status: RESOLVED NOT A BUG    
Severity: normal CC: nate
Priority: NOR    
Version: 4.2.0   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Markus Strobl 2009-02-24 04:13:28 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Gentoo Packages

For some unknown reason some of the files in .kde/share/config were not writable by the kde user. When changing various settings in systemsettings (screen saver, key bindings, etc), everything seemed normal even though the new config could not be written to disk. In some cases (key bindings) the current session used the updated config until a system restart. In other cases (screen saver), systemsettings would show the new config, but it never took effect. 

Correcting the ownership problem on the config files fixed the problem, but systemsettings should have displayed a warning when it could not write the new config to disk.

How to reproduce:
Write protect the config files in .kde/share/config. Change config in systemsettings. Press "apply". Everything looks normal (no warnings), but config is never changed.

Expected behavior:
Warning message displayed that configuration could not be saved including config file in question.
Comment 1 Andrew Crouthamel 2018-11-02 23:03:39 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 2 Andrew Crouthamel 2018-11-16 05:27:05 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 3 Markus Strobl 2018-11-17 03:44:24 UTC
Yes, this bug is still active. Just tried the following on 5.14.3:

1) chmod 000 .config/ksmserverrc

2) Opened system settings->startup and shutdown->desktop session

3) 'Confirm logout' was not selected, so I selected it.

4) Press apply

Result: No error message even though config file could not be modified.
Comment 4 Nate Graham 2020-01-23 06:26:59 UTC
Since each individual KCM is its own program, this isn't really fixable globally. Please file bugs on each KCM where you encounter this.