If gnome-screensaver isn't running, suspend wastes 5s

Bug #620013 reported by Michael Terry
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power
Confirmed
Low
gnome-power-manager (Ubuntu)
Triaged
Low
Unassigned

Bug Description

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.

Michael Terry (mterry)
tags: added: oem-services patch-forwarded-upstream
Changed in gnome-power:
status: Unknown → New
Changed in gnome-power-manager (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in gnome-power:
status: New → Confirmed
Changed in gnome-power:
importance: Unknown → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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