The manpage for acpid says that %e in the config files gets expanded to the kernel message sent to acpid. Because of an uninitialised size(of the string) in the code this is a random amount of the message. (Usually either "" or " " or a single character). This means the program is basically useless because no message parsing is possible. Reproducible: Always Steps to Reproduce: 1. Compile and run the daemon 2. Create acpi events while watching the syslog 3. Actual Results: for undefined events the message will be meaningless (ie no actual info is given) Expected Results: Given info as to what event actually occurred (via the default rule)
Created attachment 11822 [details] An ebuild to use the patch
Created attachment 11823 [details] An ebuild to use the patch
Created attachment 11824 [details, diff] Patch - adds one line to the source to fix this major bug
This looks for me as an acpid-bug. Did you send your patch to the acpid-author?
Okay, the acpid-author is working on this and will release a new version within a few days. I'll wait for that and then update the ebuild.
Got the patch from the acpid website... Thought I would add it here as I didn't know how long til its fixed upstream.
acpid 1.0.2 is out and added to portage.