Comment 33 for bug 951000

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks everyone for the work there, some comments:
- using gconftool to write the value and relying on the migration script to copy it over to gsettings is just wrong, we should stop doing that
- we didn't change it by then, there was a problem with writting to gsettings directly ... but I can't remember which one...
- comment #4 suggests that gsettings' upstream recommended using a custom dconf database as a reliable way

Did anyone try to modify /usr/sbin/guest-account to just call "dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled"? That should probably work (if the XDG_RUNTIME_DIR that stores the dconf database exists)