Forwarding an issue identified as part of this bug: https://bugs.edge.launchpad.net/ubuntu/+source/hotkey-setup/+bug/222796 [Problem] The mute key is mapped to XF86ScreenSaver rather than XF86AudioMute. [Original Report] "The mute key is recognized by gnome-power-manager as key 160, the reason seems to be a wrong mapping in X - don't know how to change that. My mute key locks the screen, same situation as described by Jane: m500286@x60:~$ acpi_listen ibm/hotkey HKEY 00000080 00001017 m500286@x60:~$ lshal -m Start monitoring devicelist: ------------------------------------------------- 16:46:36.257: computer_logicaldev_input_5 condition ButtonPressed = mute No visible X events ... Even with a stopped acpid the mute-button locks the screen. $ xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p' 160 XF86ScreenSaver " [Further Notes] xkb seems to have these mappings in settings/inet: I20 = XF86AudioMute I160 = XF86ScreenSaver For xkb_keycodes "basic", keycode 160 => I20 For xkb_keycodes "evdev", keycode 160 => I160 I've asked the reporter for their `xkbcomp -xkb :0 -` and `setxkbmap -print` and will attach when I get it.
This mapping is decided by xkeyboard-config. Evdev just passes on whatever it gets from the kernel.
Bryce, any updates?
http://launchpadlibrarian.net/19724052/hotkey-setup_0.1-23ubuntu8.debdiff
The solution does not look like it is related to xk-c...
Correct; as can be seen from the downstream bug, we ended up solving it in Ubuntu and found it had nothing to do with xkeyboard-config. In general we've had a number of bugs in Ubuntu mis-filed against xkeyboard-config that are actually hotkey problems. At UDS last month we had a hotkey conclave to discuss how to handle these going forward (see http://wiki.ubuntu.com/Hotkeys for the outcome of that). Further, yesterday I did a pass through xkeyboard-config in launchpad and moved all the hotkey-related bugs out of it, and will avoid forwarding them your way going forward. Sorry for being confused earlier on this.
No problem at all. I am glad to work with distromakers who work hard to distinguish our bugs from non-related issues. Thanks for being cooperative:)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.