touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Ah, ok; Some more ideas:

  - "sudo systemctl stop acpid", to rule out acpid and acpi-support

 - install "evtest" and run "sudo evtest", select the lid switch, and
check if you actually get an event after ~ 3 minutes? I don't actually
expect one, as logind should then log a "Lid closed." event which it
apparently doesn't; but let's verify.

Is it possible for me to get ssh access to this machine?
(https://launchpad.net/~pitti/+sshkeys, possibly via you doing an ssh
port forward to chinstrap?)

-- 
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:
  desktop machine suspends with systemd after ~3 minutes, does NOT
  suspend with upstart

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  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.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1438301/+subscriptions