I think there's more than one issue here. The ConsoleKit interaction problem is an error in the default /etc/dbus-1/system.d/ConsoleKit.conf since ConsoleKit 0.2.10 (see http://gitweb.freedesktop.org/?p=ConsoleKit.git;a=commitdiff;h=f0fb2d1cfd0f0ea3ad922175e895a9e751498a03 for fix).
However I find that fixing the config file and reloading dbus config still doesn't make the screensaver start. It seems to be starting, then instantly getting some sort of event and halting. This is confirmed when I manually lock the screen: the screen blanks but the password entry dialog box comes up instantly, as if the mouse was moved, and only clicking "cancel" makes the screensaver actually start. So I think there's a small bug in ConsoleKit (config file problem) and a larger bug in gnome-screensaver (instantly stopping) but this could also be a hardware problem or something else entirely. -- does not start in intrepid https://bugs.launchpad.net/bugs/256586 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
