registry team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

Public bug reported:

Binary package hint: gnome-power-manager

If gnome-screensaver isn't running or for whatever reason isn't
fulfilling dbus requests, when gnome-power-manager asks it to Lock
itself, g-p-m will wait 5s for the screensaver to finish locking before
timing out and continuing.

You can see this if you:
 0) Make sure you have the gconf setting to lock screensaver on suspend
 1) Close your laptop lid (note how long it takes for your computer to suspend)
 2) Open lid, resume
 3) killall gnome-screensaver
 4) Close your laptop lid again (note again how long it takes)

Both #1 and #4 should be the same length of time, but #4 actually takes
5s longer.

Really, if the Lock dbus request didn't go through, g-p-m shouldn't
waste its time waiting.

I've filed a bug upstream about it.

** Affects: gnome-power
     Importance: Unknown
         Status: Unknown

** Affects: gnome-power-manager (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: oem-services patch-forwarded-upstream

** Bug watch added: GNOME Bug Tracker #627290
   https://bugzilla.gnome.org/show_bug.cgi?id=627290

** Also affects: gnome-power via
   https://bugzilla.gnome.org/show_bug.cgi?id=627290
   Importance: Unknown
       Status: Unknown

** Tags added: oem-services patch-forwarded-upstream

-- 
If gnome-screensaver isn't running, suspend wastes 5s
https://bugs.launchpad.net/bugs/620013
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for gnome-power.