@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 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
