acpid
acpid2 is a flexible and extensible daemon for delivering ACPI events. When an event occurs, it executes programs to handle the event. These events are triggered by certain actions, such as:
- Pressing special keys, including the Power/Sleep/Suspend button
- Closing a notebook lid
- (Un)Plugging an AC power adapter from a notebook
- (Un)Plugging phone jack etc.
Installation
Install the acpid package. Then start/enable acpid.service.
Configuration
acpid comes with a number of predefined actions for triggered events, such as what should happen when you press the Power button on your machine. By default, these actions are defined in /etc/acpi/handler.sh, which is executed after any ACPI events are detected (as determined by /etc/acpi/events/anything).
The following is a brief example of one such action. In this case, when the Sleep button is pressed, acpid runs the command which should place the computer into a sleep (suspend) state:
button/sleep)
case "$2" in
SLPB) echo -n mem >/sys/power/state ;;
*) logger "ACPI action undefined: $2" ;;
esac
;;
Unfortunately, not every computer labels ACPI events in the same way. For example, the Sleep button may be identified on one machine as SLPB and on another as SBTN.
To determine how your buttons or shortcuts are recognized, run the following command:
# journalctl -f
Now press the Power button and/or Sleep button (e.g. ) on your machine. The result should look something this:
logger: ACPI action undefined: PBTN logger: ACPI action undefined: SBTN
If that does not work, run:
# acpi_listen
or with :
$ netcat -U /var/run/acpid.socket
Then press the power button and you will see something like this:
button/power PBTN 00000000 00000b31
The output of is sent to /etc/acpi/handler.sh as $1, $2 , $3 & $4 parameters.
Example:
$1 button/power $2 PBTN $3 00000000 $4 00000b31
As you might have noticed, the Sleep button in the sample output is actually recognized as SBTN, rather than the SLPB label specified in the default /etc/acpi/handler.sh. In order for Sleep function to work properly on this machine, we would need to replace SLPB) with SBTN).
Using this information as a base, you can easily customize the /etc/acpi/handler.sh file to execute a variety of commands depending on which event is triggered. See the #Tips and tricks section below for other commonly used commands.
button/power, button/lid, button/suspend and button/hibernate are handled by systemd-logind.service(8) by default, see Power management#Power management with systemd. If handling these events with acpid, the handling of these events by logind should either be disabled first, or inhibited.Alternative configuration
By default, all ACPI events are passed through the /etc/acpi/handler.sh script. This is due to the ruleset outlined in /etc/acpi/events/anything:
# Pass all events to our one handler script event=.* action=/etc/acpi/handler.sh %e
While this works just fine as it is, some users may prefer to define event rules and actions in their own self-contained scripts. The following is an example of how to use an individual event file and corresponding action script:
As root, create the following files:
Make the script executable, and reload the acpid.service to get acpid to recognize the changes to these files.
Using this method, it is easy to create any number of individual event/action scripts.
Tips and tricks
Example events
The following are examples of events that can be used in the /etc/acpi/handler.sh script. These examples should be modified so that they apply your specific environment e.g. changing the event variable names interpreted by .
To set the laptop screen brightness when plugged in power or not (the numbers might need to be adjusted, see ):
ac_adapter)
case "$2" in
AC*|AD*)
case "$4" in
00000000)
echo -n 50 > /sys/class/backlight/acpi_video0/brightness
;;
00000001)
echo -n 100 > /sys/class/backlight/acpi_video0/brightness
;;
esac
Enabling volume control
Find out the acpi identity of the volume buttons (see above) and substitute it for the acpi events in the files below.
Enabling backlight control
Similar to volume control, acpid also enables you to control screen backlight. To achieve this you write some handler, like this:
and again, connect keys to ACPI events:
/etc/acpi/events/bl_d
event=video/brightnessdown action=/etc/acpi/handlers/bl -
Enabling Wi-Fi toggle
You can also create a simple wireless-power switch by pressing the WLAN button. Example of event:
and its handler:
Disabling ordinary key events
Since b336c96 acpid generates events for some ordinary key presses, such as arrow keys. This results in event/handler spam, visible in system logs or top. Events for these buttons can be dropped in the configuration file:
Getting user name of the current display
To run commands depending on Xorg, defining the X display as well as the MIT magic cookie file (via XAUTHORITY) is required. Latter is a security credential providing read and write access to the X server, display, and any input devices (see ).
See for an example function when using xinitrc.
- If the LCD backlight is not turned off when the lid is closed, you may do so manually by running
getXuser xset dpms force offandgetXuser xset dpms force onrespectively on lid close and lid open events. Should the display be blanked, but the backlight left on, instead use vbetool withvbetool dpms offandvbetool dpms on. See also XScreenSaver#Configuration. - When using who or w, make sure
/run/utmpis created at boot-time. See utmp(5) for details.
Connect to acpid socket
In addition to rule files, acpid accepts connections on a UNIX domain socket, by default . User applications may connect to this socket.
Where can be a script similar to /etc/acpi/handler.sh.
Disable keyboard and touchpad while laptop lid is closed under Wayland
This example uses inhibited property of input device drivers as a replacement for xinput which does not work under Wayland.