acpic - an acpid client
This little daemon extends acpid
event handling capabilities. Normally, event handlers are placed by root in
/etc/acpi/events/. With acpic, you can place additional handlers in a per-user
~/.config/acpi/events/ directory.
I personally use it to control PulseAudio with hardware volume buttons on my laptop (see examples).
Installation
The easiest way is to install acpic with pip:
$ pip install acpic
Then, place your handlers in ~/.config/acpi/events/ and make acpic somehow
start when you log in, for example by creating an XDG-compliant entry in
~/.config/autostart/acpic.desktop:
[Desktop Entry]
Name=acpic
Comment=acpid event handler
TryExec=acpic
Exec=acpic
Type=Application
License
Copyright © 2018-2022 Piotr Śliwka
This work is free. You can redistribute it and/or modify it under the terms of the Do What The Fuck You Want To Public License, Version 2, as published by Sam Hocevar. See the COPYING file for more details.
Metadata
Release files for acpic 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| acpic-1.0.0.tar.gz | 3.9 kB | Without provenance | Details |
Release files / acpic-1.0.0.tar.gz
| Download URL | acpic-1.0.0.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd0f55c4235b3a6a87218dded70ab5c0d265e72c1f536b66eb6803837bcabdc8
|
|
BLAKE2b-256 checksum How to use checksums |
ab95fb84874948086308fb5d3e84dc551ab66e76723bb24612f8b06196f76662
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.10.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.10.2
|
Security for acpic 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.