Bug#919694: elogind triggers ACPI suspend on laptop lid close, contrary to prior acpi-support configuration

[Thorsten Glaser]

On Fri, 18 Jan 2019, Zygo Blaxell wrote:

> I was reporting.  I had configured acpi-support to take no suspend
> action on lid close, docked or otherwise.

Ah, so that’s where to configure this, thanks! (I fully expect closing
the lid to do either absolutely nothing or, at best, start xlock. It’s
common for me to close the laptop but have tasks running or at least
network I/O like IRC going on, and I’m aware enough to be able to su‐
spend a system myself when needed.)

> elogind appears to be unaware of acpi-support's overlapping
> functionality, and the maintainer scripts for elogind don't adjust
> elogind's configuration to disable lid/power/hibernate key handling if
> there's another ACPI event handler already installed on the system.
> Both can be installed at the same time, and by default both will try
> to suspend the system, so in the worst case you could get two
> suspend/resume cycles per lid close (which is a great way to find ACPI
> firmware bugs).

OK, so that, of course, has to be fixed ☺

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg