Bug#766991: acpid: does not process events

[Norbert Preining]

Hi Ted, hi Systemd maintainers

SHort description for systemd maintainers: acpid seems not to be
started anymore automatically, thus custom events defined in 
/etc/acpid/... are not processed anymore. In my case the touchpad
toggle key is a specific event and I have written an action that
should actually toggle the touchpad, but it is never processed,
since acpid is not started.

On Mon, 27 Oct 2014, Ted Felix wrote:
>   I've not used systemd yet, but I'm pretty sure acpid works fine
> when the socket is sent in as the stdin fd (or something along those

[what follows is my interpretation - systemd maintainers, please correct!]

It is not a problem of working or not, the problem is that
	acpid is *not* started
but only the socket kept open by systemd.

That means that events that should trigger actions are not processed.


I took a look into the acpid.service and acpid.socket files, but
I don't understand systemd.

It seems that systemd decides by itself that acpid needs no
starting, but only an open socket. systemd then opens the socket,
and listens, and in case someone wants something over the socket,
it starts acpid.

THat explains why each one of the following actions actually start
the acpid:
* /etc/init.d/acpid - of course
* acpi_listener - it pulls the socket, thus systemd starts acpid

But the point is that there are events generated from kbd that are
not coming over the socket, and thus are completely lost.

All the best

Norbert

------------------------------------------------------------------------
PREINING, Norbert                               http://www.preining.info
JAIST, Japan                                 TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------