void-linux / void-linux/void-docs
Acpid: Better document the events/anything file
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 217
- Forks
- 212
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
In the Power Management section, acpid and elogind are both mentioned, along with the incompatibility between them. However, the only documented "solution" is to completely disable acpid (which breaks things like acpi_listen) or completely remove acpi handling from elogind (which break proper sleep/etc handling in DEs which use it).
In reality, commenting out or removing /etc/acpi/events/anything is enough to disable the handlers on the acpid side. This is a 3rd option, and the only one of these that works when both elogind's handling is needed by a DE and the acpid socket (or custom handlers) are required. Perhaps this could be mentioned as a solution when disabling acpid or elogin's handlers is not possible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Find the Power Management section in the Void Linux documentation and review its discussion of acpid and elogind. Document commenting out or removing /etc/acpi/events/anything as an additional option, and verify that the section explains when this preserves both elogind handling and acpid socket or custom-handler access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100