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 ** Bug watch added: GNOME Bug Tracker #693149 https://bugzilla.gnome.org/show_bug.cgi?id=693149 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1122028 Title: gsettings does not respect dconf locks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1122028/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
