Ubuntu
gnome-screensaver package

does not start in intrepid

Bug #256586 reported by Timo Aaltonen
This bug report is a duplicate of:  Bug #278112: Screensaver doesn't start. Edit Remove
6
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: gnome-screensaver

The screensaver does not start.. something wrong with the interaction with consolekit:

[gs_listener_update_console_kit_idle] gs-listener-dbus.c:321 (13:07:56): org.freedesktop.DBus.Error.AccessDenied raised:
 A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.ConsoleKit.Session" member "SetIdleHint" error name "(unset)" destination "org.freedesktop.ConsoleKit")

console-kit-daemon is running.

Revision history for this message
Martin Pitt (pitti) wrote :

Works fine for me. Maybe you did not reboot after the latest d-bus restart?

Changed in gnome-screensaver:
status: New → Incomplete
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Maybe not right after the update, but did today when there were another set of updates. I also dist-upgraded my home desktop this weekend, and noticed this problem there first.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I still have this problem on both my laptop and home desktop after todays updates, also with a new user. Also, I have another laptop which _doesn't_ suffer from this..

Revision history for this message
nullack (nullack) wrote :

Confirmed - replicating the issue on clean Alpha 4 build with repo updates as per current 18/08/08

Changed in gnome-screensaver:
status: Incomplete → Confirmed
Revision history for this message
sojourner (itsmealso2) wrote :

also confirming for intrepid amd64 alpha 4 up to date as of august 18 .

Revision history for this message
Ben Aisen (beinsane11) wrote :

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.

Revision history for this message
Ben Aisen (beinsane11) wrote :

...and it appears that the latter bug is a compiz problem. When I switch window managers to metacity the screensaver works fine.

In any case, this is not a bug in gnome-screensaver.

Revision history for this message
Ben Aisen (beinsane11) wrote :

See bug 159263 for a workaround to the compiz issue (works for me).

Revision history for this message
harvest316 (harvest316) wrote :

Compiz workaround didnt change anything, but the ConsoleKit.conf fix sorted me out.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.