gnome-screensaver should depend on dbus-1-utils

[Michael Bienia]

I've installed gnome-screensaver and it didn't work. It only complained that it can't connect to dbus. After some searching I finally found out, that I had also to install dbus-1-utils.

Shouldn't therefore gnome-screensaver depend on dbus-1-utils?

[Trent Lloyd (lathiat)]

This doesn't appear to be current, it works fine here with dbus-1-utils.

Could you check if this is still broken, and additionally, if still broken, what specifically breaks without dbus as i can start the daemon, change prefs and activate the screensaver fine.

[Trent Lloyd (lathiat)]

Err typo above, it works fine *without* dbus-1-utils.

[Venkat Raghavan (venkatraghavan)]

Works fine with dbus-1-utils

Without dbus-1-utils, it launches fine. It locks the screen fine, and after entering my password, i get this.. (in terminal)

First run:

** Message: set DPMS timeouts: 0 0 0.
The program 'gnome-screensaver' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 145789 error_code 3 request_code 15 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line**

Run 2:
** Message: set DPMS timeouts: 7200 7200 14400.
The program 'gnome-screensaver' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 4577 error_code 3 request_code 15 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
   option to change this behavior.

[Trent Lloyd (lathiat)]

OK so this has nothing to do with d-bus

since this is a separate bug and gnome-screensaver is now in main can you please file a bug against it on bugzilla

[Michael Bienia (geser)]

I did check again, but without dbus-1-utils is doesn't work for me.

I did remove dbus-1-utils for the test:
rc dbus-1-utils 0.36.2-0ubuntu3
ii gnome-screensaver 0.0.13-0ubuntu3

I can change the preferences but gnome-screensaver doesn't start and when I select System->Lock Screen nothing happens.

When I start gnome-screensaver in a terminal I get the following output:
$ gnome-screensaver

** (gnome-screensaver:5417): CRITICAL **: couldn't connect to session bus: Unable to determine the address of the message bus
** Message: set DPMS timeouts: 7200 7200 14400.

** (gnome-screensaver:5417): WARNING **: failed to register with the message bus

If it matters this is an uptodate breezy on an amd64 which was once (6 months ago) a Debian box.