Created attachment 100226 [details] [review] keymap rule which fixes the micmute button The micmute button on the Plantronics .Audio 626 DSP headset is recognized as some kind of keyboard modifier and messes up xorg input when it's turned ON. This is all I needed to add to /lib/udev/rules.d/95-keymap.rules on Debian (udev 204-8) to fix it: ENV{ID_VENDOR_ID}=="047f", ENV{ID_MODEL_ID}=="c006", RUN+="keymap $name 0xb002f micmute"
Converted for the hwdb and applied as http://cgit.freedesktop.org/systemd/systemd/commit/?id=9e3dbf6b. Please check that it works properly.
(In reply to comment #1) > Converted for the hwdb and applied as > http://cgit.freedesktop.org/systemd/systemd/commit/?id=9e3dbf6b. Please > check that it works properly. The 'f' needs to be an 'F'?
Oops, thanks for catching this. BTW., I used F20 because some other entry uses it. But now I see that input.h has KEY_MICMUTE = 248. Shouldn't this be used instead in both cases?
FTR: The "F20" assignment for "mic mute" was done in X.org in https://bugs.freedesktop.org/show_bug.cgi?id=54171 . Apparently at a time when KEY_MICMUTE either did not yet exist in the kernel's input.h or it had a key code > 255 so that X.org couldn't handle it. So we first need to adjust xkeyboard-config to also recognize KEY_MICMUTE as XF86AudioMicMute, and after that has been out in the wild for some time, switch the keymaps away from F20. But that would mean a regression for people who still have an older xkeyboard-config, so I propose we keep F20 for at least a year or so. I also left a comment in bug 54171 about that.
Update: X.org can only handle key codes < 248, thus KEY_MICMUTE is the first one that doesn't work any more. See followups on bug 54171. So we'll keep F20 for the time being.
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.