[Ubuntu Wiki] Update of "Hotkeys/Troubleshooting" by pitti

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "Hotkeys/Troubleshooting" page has been changed by pitti:
http://wiki.ubuntu.com/Hotkeys/Troubleshooting?action=diff&rev1=36&rev2=37

Comment:
update to the current world

  Hotkey and 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:
  
  Packages involved in acting on hotkey events:
-  * gnome-power-manager - handles brightness and power hotkeys.  Displays a popup 'OSD' display
-  * gnome-settings-daemon (handles media keys and visual feedback, display toggling)
+  * gnome-settings-daemon (handles media, brightness, and power keys and visual feedback, display toggling)
   * gnome-control-center (gnome-sound-properties, gnome-keybinding-properties)
   * acpi-support (deprecated, being phased out)
-  * gdm (until Ubuntu 9.04; 9.10 uses gnome-power-manager in gdm)
  
  Packages involved in propagating hotkey events to where they belong:
   * linux kernel
@@ -19, +17 @@

   * xserver-xorg-input-evdev
   * xkeyboard-config
   * acpi-support (deprecated, being phased out)
-  * hal (until Ubuntu 9.04; deprecated)
-  * hal-info (until Ubuntu 9.04; deprecated)
-  * hotkey-setup (until Ubuntu 9.04; deprecated)
  
  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.
  
  === Step-by-step Troubleshooting ===
  
- /!\ '''NOTE:''' You need to run Ubuntu 9.10 ("Karmic Koala") or newer for this; running these commands from a live system will work, so you do not need to actually have the Ubuntu development release installed. Since the hotkey architecture changed in Ubuntu 9.10, we cannot use debugging information collected on older Ubuntu releases.
- 
-  1. if `gnome-settings-daemon` or `gnome-power-manager` is running, stop it first with `killall gnome-settings-daemon gnome-power-manager`; these daemons grab some X events exclusively and prevent them from being seen with `xev`.
+  1. if `gnome-settings-daemon` is running, stop it first with `killall gnome-settings-daemon`; these daemons grab some X events exclusively and prevent them from being seen with `xev`.
   1. run `xev` to test whether a keypress event is seen: {{{
  xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p'
  }}}