touch-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

Yes, per IRC, this is more or less the expected behavior of both systemd
(logind) and upstart (poweroff).  It's only the emergent behavior
combined with a buggy kernel/hardware button behavior that's surprising.

As noted on IRC, there are three possible solutions:
 1) get the kernel fixed to not produce rapid-fire 'power button' events
 2) adjust logind to not process further poweroff events while one is still running (which requires special knowledge to know this is the case, since 'poweroff' returns immediately)
 3) change 'poweroff' itself to not behave this way when called by logind

I understand you've opted for option 1), which is what I recommended.

I am not closing this bug report as invalid, because while the trigger
condition here is a kernel/hardware bug, it's still unexpected behavior
that someone hitting the power button twice in quick succession on a
server would cause an unclean shutdown, and we should ultimately also
fix this via 2) or 3) as well.

** Changed in: systemd (Ubuntu)
       Status: Incomplete => New

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

Title:
  systemd-logind triggered poweroffs ignore upstart services

Status in “systemd” package in Ubuntu:
  New

Bug description:
  systemd-logind has a facility to detect non-ACPI power-off events
  (e.g. a power button push) and initiate a system shutdown. This
  facility works in Ubuntu - it manages to shutdown the sysvinit
  services, but upstart services do not appear to be cleanly shutdown.
  Among other things, it means that local filesystems don't get properly
  unmounted.

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