Background: logind has some "failsafe" logic to go to suspend after 30 s if the lid is closed and there are no external monitors connected (http://cgit.freedesktop.org/systemd/systemd/commit/?id=ed4ba7e4f65215). This would lead to effects like this if the lid switch is broken and always says "closed" (like in bug 1438301), and monitor detection fails (like in this case - /sys/class/drm does not have multiple outputs).
So there are two things to fix here:
- Investigate why on this system the lid switch always reports "closed"
- Dial back the failsafe to not get engaged if the lid switch reports "closed" right from the start when systemd boots. In that case it's clearly broken, as "normal" laptops don't boot with the lid closed.
Background: logind has some "failsafe" logic to go to suspend after 30 s if the lid is closed and there are no external monitors connected (http:// cgit.freedeskto p.org/systemd/ systemd/ commit/ ?id=ed4ba7e4f65 215). This would lead to effects like this if the lid switch is broken and always says "closed" (like in bug 1438301), and monitor detection fails (like in this case - /sys/class/drm does not have multiple outputs).
So there are two things to fix here:
- Investigate why on this system the lid switch always reports "closed"
- Dial back the failsafe to not get engaged if the lid switch reports "closed" right from the start when systemd boots. In that case it's clearly broken, as "normal" laptops don't boot with the lid closed.