The microphone mute key yields Linux key input event KEY_MICMUTE which has the value 248. Add 8 to get the X KeyCode number, you get 256. This is greater than the maximum KeyCode that X handles, 255.
See: http://www.x.org/wiki/XI2 The problem is similar to the problem with the Zoom hotkey combination on the X220, Fn-Space. The key combination yields KEY_ZOOM, value 372. The corresponding X KeyCode, 380, is also above 255. A workaround is to remap the keycodes to ones that X can handle. See: http://www.thinkwiki.org/wiki/Installing_Ubuntu_11.04_(Natty_Narwhal)_on_a_ThinkPad_X220#Fix_for_hotkey_shortcomings (This page doesn't describe a way to control the LED on the Microphone Mute key.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “udev” package in Ubuntu: Fix Released Status in “xserver-xorg-input-evdev” package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 00000080 0000101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x3400001, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x3400001, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/408903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
