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) ** Changed in: lightdm (Ubuntu) Importance: Low => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
