@Sebastien, thanks for your reply. I have tried the patch; it works good as expected and I have no issue with it.
The reason I tried "dbus-launch gsettings set org.gnome.desktop.lockdown disable-lock-screen true" was because you commented on our private bug and ask us to try dbus-launch. Therefore, I assumed you still expected my reply. Your patch works perfectly on the machine I tested, but I still hope to understand the reason why dbus-launch gsettings does not work for you. In the old guest-account, it does the following su $USER <<EOF gconftool-2 --set --type bool /desktop/gnome/lockdown/disable_lock_screen True EOF Since it su to guest user, it is reasonable to me that the gsetting can be set properly for guest user, and that is also what I see when I made tests to use "dbus-launch gsettings". I will be very happy to know what kind of difference causes "dbus-launch gsettings" not function in your side but my side. -- 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: Confirmed Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Precise: Triaged Status in “lightdm” source package in Raring: Fix Committed Bug description: * Impact: sometime screen locking doesn't get disabled in guest session * Test Case: - log into a guest session - try locking the screen screen locking should be disabled * Impact: check that screen locking is well disabled in guest sessions 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
