Hello Folks,
Posting here because while there was a gconf mail list there is no dconf mail list - apologies if there is somewhere else I should be posting to instead.
Onto the problem at hand - No matter what I set via gsettings or dconf policy files, my session idle timeout kicks in at exactly 300 seconds (RHEL default I gather) and locks the session.
I am trying to determine the most correct way to set this programmatically (needs to be done via Puppet emplacement of files or 'Exec' commands) so that it can be pushed out to all our desktops and comply with STIGs.
Here is what I have (30 seconds was just to test that the setting worked, which it never did. The real value would be 900):
$dconf read /org/gnome/desktop/session/idle-delay
uint32 30
$gsettings get org.gnome.desktop.session idle-delay
uint32 30
$cat /etc/dconf/db/local.d/00-screensaver
[org/gnome/desktop/session]
# Set the lock time out to 900 seconds before the session is considered idle.
idle-delay=900
[org/gnome/desktop/screensaver]
# Set this to true to lock the screen when the screensaver activates
lock-enabled=true
# Set the lock timeout to 0 seconds after the screensaver has been activated
lock-delay=0
Even with all of the above settings set, it locks at neither 30 seconds nor 900 seconds, but always at the RHEL default of 300 seconds.
I've grepped all through /etc/dconf/db for '300' trying to find a leftover setting that is causing this to no avail. Does anyone have any ideas?
Here are my dconf/RPM version btw: dconf-0.22.0-2.el7.x86_64
Thanks very much!
- Kodiak Firesmith
_______________________________________________ gnome-list mailing list gnome-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gnome-list
