dx-packages team mailing list archive

Thread
Date

[Bug 1201180] Re: powerbtn.sh conflicts with logind

To: dx-packages@xxxxxxxxxxxxxxxxxxx
From: Erik Hovland <erik@xxxxxxxxxxx>
Date: Tue, 06 Oct 2015 21:33:07 -0000
Reply-to: Bug 1201180 <1201180@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

I can confirm that systemd logind is in control of the power button on
my ASUS UX305 laptop as of Kubuntu 15.04. This means that no matter what
the settings in KDE system-settings the power button is handled by
logind.

Since the power button is right above backspace and I often hit the backspace key (and have accidentally shut off my laptop several times) I have changed the line in /etc/systemd/logind.conf to:
HandlePowerKey=ignore

This renders the power key useless, but that is better then accidentally
shutting my computer off in the middle of typing.

If logind is going to "handle" the power key, maybe system-settings
should deal with logind and not acpi or whatever else system-settings is
trying modify to get configuration control of the power key?

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1201180

Title:
  powerbtn.sh conflicts with logind

Status in acpid package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released
Status in kde-workspace package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Invalid

Bug description:
  In saucy the PC powers down as soon as I press the power button, it
  seems that systemd is calling "poweroff", but I'm not sure if it's
  doing that in response of some other event (i.e. as callback of a dbus
  call):

  root      4998  0.0  0.0 177932  2104 ?        Sl   20:41   0:00 /usr/lib/x86_64-linux-gnu/systemd-shim
  root      5012  0.0  0.0   4440   624 ?        S    20:41   0:00  \_ sh -c /sbin/poweroff
  root      5013  0.0  0.0   4440   628 ?        S    20:41   0:00      \_ /bin/sh /sbin/shutdown -h -P now

  In any case the caller or systemd itself should be aware that there's
  a session-manager running and that it shouldn't actually directly
  power off the system then.

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