hal with acpi use flag enabled unconditionally enables interfaces for procfs and acpid, what result in regular log records that hald can not connect to acpid. In the attachment you can find patch that checks both and adjust configure arguments accordingly. May be some additional wording required in warning hal ebuild issues on merge. I leave it to native speakers. Reproducible: Always Steps to Reproduce: 1. delete acpid 2. build hal with acpi use flag 3. start hal 4. check system logs Actual Results: errors in the log Expected Results: no errors
Created attachment 185196 [details, diff] patch that fixes described issue
I believe this is by design. The logic is that hal can listen to kernel events but acpid is needed for any kind of user customization/dispatching and hal then gets events from acpid anyway (and X too btw). Could you explain a bit more what you are expecting ?
(In reply to comment #2) > Could you explain a bit more what you are expecting ? As far as I know procfs is deprecated and hal can read info from sysfs. At least sysfs has info about batteries and I see logs when power button is pressed. At this point acpid is optional dependency. If acpid is not installed, but acpi flag is used then hal bloat logs with errors that it can not connect to the acpid server via socket. I couldn't find any config where I can silence this error, so I propose this patch for inclusion.
you're not understanding how this information is used. The /proc interface that's used is very much in use and the only method. All ACPI events are sent out via /proc/acpi/event and that's what this functionality relates to. The reading of other ACPI data, such as battery information is done via sysfs already by HAL for a long time. ACPI events are things like button presses. The /proc/acpi/event interface only allows for 1 listener, HAL will happily be that listener. However some people have external apps that either need to listen to that interface, at which point acpid will listen to that interface and provide a unix socket which multiple applications can listen to, that contain the same data from /proc/acpi/event. Additionally, acpid can also parse the event and execute scripts based on the event. That being said, I'm closing the bug invalid since you're being confused about the ACPI usage.
