Hotkeys
|
Size: 642
Comment:
|
Size: 2194
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = ACPI Hotkeys = |
|
| Line 9: | Line 7: |
| == | == Hotkey Debugging Guide == === Involved Components === ACPI events cross a lot of different layers, and determining the component that is handling them can take quite a bit of digging. Below is a non-comprehensive list of components which have been known to handle hotkey events: Most commonly at fault: * gnome-power-manager - handles brightness and power hotkeys. Displays a popup 'OCD' display * pm-utils * hotkey-setup * acpi-support Less commonly at fault: * acpid * linux kernel * xorg * gdm Note that the 'acpi' source package is *not* involved in any of this, although many acpi/hotkey issues get (incorrectly) filed against it. 'acpi' is just a command line tool for listing info about acpi devices. === Useful Information to Collect === === Troubleshooting Tricks and Tips === * Testing: Before making changes, make a list of all your keys and hit each of them in turn, and record how they work. Repeat this after every change, so you'll know if a change fixed one thing but broke something else. * Running acpid in debug mode: acpid -d. This should display output for software events when hitting hotkeys. * Disable different suspects. If the issue goes away or changes behavior with one of these turned off, and comes back when it's on, then that strongly points to an issue in that particular component: * gnome-power-manager: pkill -9 gnome-power-manager * hotkey-setup: /etc/init.d/hotkey-setup stop * gdm: From console, /etc/init.d/gdm stop; startx * == Hotkey Architecture == |
Laptops have special functions such as sleep or brightness that are implemented through either buttons outside the main keyboard or key combinations using the Fn key. These are called "hotkeys", and are typically implemented in the laptop hardware and BIOS via the Advanced Configuration and Power Interface (ACPI).
NOTE: This document is a work in progress. ACPI is a complex subsystem and impossible for any one person to fully understand. Please take a few minutes to improve this document with the bits you know!
Hotkey Debugging Guide
Involved Components
ACPI events cross a lot of different layers, and determining the component that is handling them can take quite a bit of digging. Below is a non-comprehensive list of components which have been known to handle hotkey events:
Most commonly at fault:
- gnome-power-manager - handles brightness and power hotkeys. Displays a popup 'OCD' display
- pm-utils
- hotkey-setup
- acpi-support
Less commonly at fault:
- acpid
- linux kernel
- xorg
- gdm
Note that the 'acpi' source package is *not* involved in any of this, although many acpi/hotkey issues get (incorrectly) filed against it. 'acpi' is just a command line tool for listing info about acpi devices.
Useful Information to Collect
Troubleshooting Tricks and Tips
- Testing: Before making changes, make a list of all your keys and hit each of them in turn, and record how they work. Repeat this after every change, so you'll know if a change fixed one thing but broke something else.
- Running acpid in debug mode: acpid -d. This should display output for software events when hitting hotkeys.
- Disable different suspects. If the issue goes away or changes behavior with one of these turned off, and comes back when it's on, then that strongly points to an issue in that particular component:
- gnome-power-manager: pkill -9 gnome-power-manager
- hotkey-setup: /etc/init.d/hotkey-setup stop
- gdm: From console, /etc/init.d/gdm stop; startx
Hotkey Architecture
See Also
Hotkeys (last edited 2009-07-08 14:31:12 by pD9EB7542)