Actually it strikes me that it should probably be the guest-session- launch script itself which should check the gconf key, and then lock or not. This would then be closest to how things should behave in an ideal world. But doing the gconf check from C is a lot faster, so Gunnar's branch looks great to me. It won't change the default behaviour, but will respect the user configuration.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/636693 Title: Premature lock when launching guest session -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
