This bug was also reported in GNOME's bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=693149
Let me add that if the locks are removed from the /etc/dconf files, and then the user changes the value manually, for example to 3 minutes, then this is the result:
$ dconf read /org/gnome/desktop/session/idle-delay uint32 180 $ gsettings get org.gnome.desktop.session idle-delay uint32 180
But if the locks are then restored (by editing the files and then running dconf update):
$ dconf read /org/gnome/desktop/session/idle-delay 10 $ gsettings get org.gnome.desktop.session idle-delay uint32 600
This bug was also reported in GNOME's bugzilla: /bugzilla. gnome.org/ show_bug. cgi?id= 693149
https:/
Let me add that if the locks are removed from the /etc/dconf files, and then the user changes the value manually, for example to 3 minutes, then this is the result:
$ dconf read /org/gnome/ desktop/ session/ idle-delay desktop. session idle-delay
uint32 180
$ gsettings get org.gnome.
uint32 180
But if the locks are then restored (by editing the files and then running dconf update):
$ dconf read /org/gnome/ desktop/ session/ idle-delay desktop. session idle-delay
10
$ gsettings get org.gnome.
uint32 600