The runscript, that comes with openrc-0.7.0 seems to prevent acpid-2.0.6 from loading my configuration. If I invoke it simply with bash, it works fine. Even if I invoke the execute line of /etc/init.d/acpid (start-stop-daemon --start --quiet --exec /usr/sbin/acpid -- ${ACPID_OPTIONS}), it works. Note, that ACPID_OPTIONS is unset. But if I use /etc/init.d/acpid or /etc/init.d/local, the configuration seems to be invisible for acpid, which is started. I´ll attach my configuration files. Reproducible: Always Steps to Reproduce: 1. Use my configuration files. 2. Restart acpid: # /etc/init.d/acpid restart Actual Results: Acpid starts, but does not do anything on the configured event. (button/lid -> xscreensaver not locked) Expected Results: Acpid starts, and does the configured command. (button/lid -> xscreensaver lock) If the configuration in general is not read, you should be able to use different events. Use a different command, for example xmessage, which does not need the xscreensaver-dependency.
Created attachment 263911 [details] lid-button configuration file in /etc/acpid/events/
Created attachment 263913 [details] script assigned to button/lid event in /etc/acpi/actions/ I did mean /etc/acpi/events/ above of course.
So your shell had $DISPLAY exported from running X, but openrc wouldn't have $DISPLAY set, and xscreensaver would have no idea where to run Looks to be like a bug in the user-supplied attached scripts, rather than openrc
Closing as WORKSFORME, export proper $DISPLAY for executing stuff in the X, if that doesn't solve it, reopen
