closing lid does not suspend in the first 3 minutes after boot
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | systemd (Ubuntu) |
Medium
|
Martin Pitt | ||
Bug Description
Right after booting, closing the lid does not cause a suspend. logind does see the lid close/open event, but there is no suspend. After some minutes this starts working, and from then on always works.
| Changed in systemd (Ubuntu): | |
| assignee: | nobody → Martin Pitt (pitti) |
| status: | New → Triaged |
| tags: | added: systemd-boot |
| Changed in systemd (Ubuntu): | |
| importance: | Undecided → Medium |
| summary: |
- closing lid does not suspend during the first couple of minutes + closing lid does not suspend while system is not fully booted |
| Martin Pitt (pitti) wrote : | #2 |
Turns out this was actually intentional. A recent upstream commit improved this: http://
With that the "dead" time got reduced from 3 mins to 30s, which ought to be fine.
| Changed in systemd (Ubuntu): | |
| status: | Triaged → In Progress |
| summary: |
- closing lid does not suspend while system is not fully booted + closing lid does not suspend in the first 3 minutes after boot |
| Launchpad Janitor (janitor) wrote : | #4 |
This bug was fixed in the package systemd - 219-7ubuntu3
---------------
systemd (219-7ubuntu3) vivid; urgency=medium
* logind autopkgtest: Add test for suspending on lid switch close.
This reproduces LP #1444166 (lid switch not working in the first few
minutes after boot).
* Reduce the initial suspend supression time from 3 minutes to 30 seconds,
and make it configurable. (LP: #1444166)
-- Martin Pitt <email address hidden> Sat, 18 Apr 2015 17:06:08 +0100
| Changed in systemd (Ubuntu): | |
| status: | Fix Committed → Fix Released |


I get that on my system while NetworkManager- wait-online. service is still running, and the system is still in "booting" state. Seth gets it due to a failed ureadahead.service and the system is degraded.