This looks like an effect of http://cgit.freedesktop.org/systemd/systemd/commit/?id=ed4ba7e4f65215. This introduced logic which deliberately checks for a closed lid and suspends the machine again, to guard against wakeups which happen when a laptop lid is closed (and the machine is potentially being carried around in a bag). The root cause of this is that this hardware reports a lid switch and reports it as closed, while there actually is no lid switch. This will probably confuse other power management bits like unity-settings-daemon or upowerd as well.
This is being detected by http://cgit.freedesktop.org/systemd/systemd/tree/src/login/logind- button.c#n275 in button_check_switches(). upower --dump confirms this as well: lid-is-closed: yes lid-is-present: yes ** Changed in: systemd (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1438301 Title: suspends after a few minutes on machines with a bogus (closed) lid switch Status in systemd package in Ubuntu: Triaged Bug description: On a desktop machine which claims to have a closed lid (on the motherboard), but doesn't actually have a lid, logind will suspend the machine shortly after boot as a safety measure to avoid burning your laptop in a bag. This is wrong in the above situation where the announced lid switch does not exist or isn't actually closed. Workaround: Set HandleLidSwitch=ignore in /etc/systemd/logind.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1438301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
