After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 709648 - 30 seconds delay to suspend is too long
30 seconds delay to suspend is too long
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: power
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2013-10-08 14:38 UTC by Allison Karlitskaya (desrt)
Modified: 2014-04-25 10:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Allison Karlitskaya (desrt) 2013-10-08 14:38:11 UTC 
g-s-d contains a 30 second timer for suspend in certain cases (like undocking with the lid closed).

30 seconds is entirely too long.  Unless I specifically know about this timeout and how long it is, I'm likely to undock my laptop, look at the suspend LED... wait for about 10 seconds... and get frustrated that, yet again, Linux suspending my laptop is unreliable.  At this point I'll open and close it manually in order to "properly" suspend.

I think the timeout needs to be decreased to (ideally) 5 seconds or at absolute most 10.  Opening the lid after undocking a laptop or removing a VGA cord can't possibly take longer than that, and if it does, the laptop will sleep and be woken again by the lid-open.
Comment 1 Bastien Nocera 2014-04-25 10:28:56 UTC 
Fixed for gnome 3.14.

commit b50d27cfcc0340be9e5a7730422ccc6e7a6af2d3
Author: Bastien Nocera <hadess@hadess.net>
Date:   Fri Apr 25 12:28:20 2014 +0200

    power: Lower the lid safety timeout
    
    To 8 seconds.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=709648