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 Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings Status in OEM Priority Project: New Status in “lightdm” package in Ubuntu: Triaged Bug description: bug # 275768 seems to be back in precise. My guest session is locking, when there is no password to unlock. I switched to the guest session from my admin account. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
