touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

At this point we have two options:

(1) fix the kernel or hardware to not claim that there's a closed lid
(2) disable that safety feature and cause some laptops to burn in your bag again

If possible, I'd like to keep this and fix (1), but if this turns out to
affect too many machines we might also go with (2).

** Description changed:

- For reasons I cannot fathom, my development server goes into deep
- suspend after ~3 minutes after startup with systemd, however, if I boot
- with upstart it does not.   This happens everytime I boot with systemd,
- the machine just goes into a deep suspend without me requesting it.
+ 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.
  
- I enabled "debug"; attached is a gzip'd syslog showing the activity -
- look at the end of the log, it goes into deep suspend. No idea why.
- 
- acpi_listen is showing some curious audio plug/unplug events that seem
- to occur on this development box, so maybe these are being
- misinterpreted as suspend events.
- 
- $ acpi_listen
- jack/headphone HEADPHONE plug
- jack/headphone HEADPHONE unplug
- jack/headphone HEADPHONE plug
- jack/headphone HEADPHONE unplug
- jack/headphone HEADPHONE plug
- jack/headphone HEADPHONE unplug
- 
- ..but I am not seeing any other ACPI related events that could be
- triggering a suspend request from acpi_listen.
+ Workaround: Set HandleLidSwitch=ignore in /etc/systemd/logind.conf

** Changed in: systemd (Ubuntu)
   Importance: High => Low

** Summary changed:

- desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart
+ suspends after a few minutes on machines with a bogus (closed) lid switch

-- 
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