<div dir="ltr">Hello Reinhard, thanks for the reply.<div><br></div><div>The odd thing with path searching in KDE 4 is that it doesn't seem to work the way I would think based on the output of the kde4-config command. For example:</div><div><br></div><div><div>kde4-config --path config</div><div>/home/kodiak/.kde/share/config/:/etc/kde/:/usr/share/kde-settings/kde-profile/default/share/config/:/usr/share/config/</div></div><div><br></div><div>^^The above made me think I could just put a file called kscreensaverrc in /etc/kde/ and have it be read. Not so. But despite not being in the config path, I *can* put the required stanza into /etc/kde4rc and have it read in properly and apply.</div><div><br></div><div>In the Red Hat way of doing things at least, not sure on Debian and such, we use /etc/ extensively so my hope was that I could at least add custom config files in /etc/kde/share/config/ that would be global for an entire host. </div><div><br></div><div>I'm not sure I understand completely about your statement on setting a custom config path for all users, I am guessing a supplemental script in addition to /etc/profile.d/kde.sh, that sets something similar to what is exported for QT_PLUGIN_PATH but for config files?</div><div><br></div><div>If that is the case, then wouldn't a user be able to easily break out of that by modifying their own environment variables for the configuration path after logging in? I really think the key to being able to confidently assert that settings are forced would be to have these settings set, enforced, and immutable completely separate from the user's particular environment (thus an augment to /etc/kde4rc or similar)...</div><div><br></div><div>But regardless of where I end up setting them, there is absolutely something wonky that I can't sort out where 'LockGrace=$milliseconds" is simply not working (the simple lock comes on w/ a password prompt, but no matter how much time passes, the screen just opens right up at the first mouse movement...)</div><div><br></div><div>Thanks again!</div><div> - Kodiak </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 21, 2017 at 5:42 AM, Reinhard Hennig <span dir="ltr"><<a href="mailto:reinhard.hennig@ofd-z.niedersachsen.de" target="_blank">reinhard.hennig@ofd-z.niedersachsen.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">Am 20.06.2017 um 17:53 Uhr schrieb Kodiak Firesmith:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Folks,<br>
I support a 95% Gnome 3 environment and am currently working on policies<br>
to help lock down alternate desktop managers.<br>
<br>
I spent a few minutes googling and came up empty, so I set the preferred<br>
settings I wanted manually and looked for the corresponding ~/.kde/ file<br>
that it changed, discovered kscreensaverrc. That gave me the format I<br>
wanted.<br>
<br>
Then I skimmed the KDE kiosk guidance and found out about the [$i]<br>
thing, eg: [ScreenSaver][$i] to make the settings immutable.<br>
<br>
I looked for system-level configs for KDE in /etc and was saddened to<br>
discover no location in /etc/ to make a global override. Then I went<br>
digging through /usr/share/kde-settings and ended up putting this file:<br>
<br>
# cat<br>
/usr/share/kde-settings/kde-pr<wbr>ofile/default/share/config/ksc<wbr>reensaverrc<br>
[ScreenSaver][$i]<br>
Enabled=true<br>
LegacySaverEnabled=true<br>
Lock=true<br>
LockGrace=10<br>
PlasmaEnabled=false<br>
Saver=kblank.desktop<br>
Timeout=1200<br>
<br>
It did succeed in graying out these settings in the GUI for users<br>
globally, but it doesn't ever seem to force the blank locking<br>
screensaver to come on and lock.<br>
<br>
So my questions are:<br>
1. Does anyone have advice on making this work?<br>
2. Is there a reason I am missing for these sorts of things not living<br>
in /etc/kde somewhere? It is my understanding that config files should<br>
always live in /etc/. That's where we tell Puppet to put most things of<br>
this nature.<br>
<br>
Thanks!<br>
- Kodiak Firesmith<br>
</blockquote></div></div>
Hi,<br>
<br>
our administration is using kde3.5 and will be switching to kde5.8 in a couple of months, so kde4 isn´t on the plan anymore but I am experienced using it. First you should check you config-path:<br>
<br>
kde4-config --path config<br>
<br>
to enforce global settings you should rather lock down your configuration using a user profile that provides its own config-path that is located before the users config path ($HOME/.kde4/share...) than<br>
modifying system files like /etc/kde4/share/config/kscreen<wbr>saverrc<br>
that will spoil your distribution and cause some problems with updates.<br>
<br>
Locking down using a user config file<br>
($HOME/.kde4/share/config/kscr<wbr>eensaverrc) will not be save because the user might edit the file and remove the immutable flag.<br>
<br>
/etc/kde4rc is not suitable for setting screensaver options.<br>
<br>
B.R.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Reinhard Hennig<br>
------------------------------<wbr>--------------------<br>
Oberfinanzdirektion Niedersachsen<br>
- IuK 381 -<br>
Am Waterlooplatz 3<br>
30169 Hannover<br>
<br>
Tel: 0511/101-3417<br>
mailto: <a href="mailto:reinhard.hennig@ofd-z.niedersachsen.de" target="_blank">reinhard.hennig@ofd-z.niedersa<wbr>chsen.de</a><br>
<br>
<br>
</font></span></blockquote></div><br></div>