Comment 5 for bug 306310

As a test, I killed gnome-power-manager, and started it up again in a window with --no-daemon so that I could see the results. I then did a suspend, woke it up, woke it up again. Saw the output, and decide to suspend again. Did so, and then had to wake it up three times, with the third one being the charm.

Here is the result:

============================================================

root@jaunty:~# gnome-power-manager --no-daemon# gnome-power-manager --no-daemon

** (gnome-power-manager:11454): WARNING **: DBUS error: Could not get owner of name 'org.gnome.ScreenSaver': no such name
** (gnome-power-manager:11454): DEBUG: proxy is NULL, maybe the daemon responsible for org.gnome.ScreenSaver is not running?

------------- MANUALLY SUSPENDED HERE -----------------

** (gnome-power-manager:11454): WARNING **: DBUS timed out, but recovering

** (gnome-power-manager:11454): WARNING **: Suspend failed without error message

** (gnome-power-manager:11454): WARNING **: Suspend failed without error message

------------- MANUALLY SUSPENDED AGAIN HERE -----------------

** (gnome-power-manager:11454): WARNING **: Suspend failed without error message

** (gnome-power-manager:11454): WARNING **: Suspend failed without error message

** (gnome-power-manager:11454): WARNING **: Suspend failed without error message

============================================================

Notice the output: "Suspend failed without error message". Suspend worked each time, but it is interesting that there is one copy of that message for each sleep that happens. The first one is the one I initiate, and the subsequent ones are the automatic cycling.