Open jturner314 opened 11 years ago
I just noticed that there is a mapping in /lib/udev/hwdb.d
that maps the mute button from the thinkpad_acpi
driver to a keycode. The relevant mapping is:
keyboard:name:ThinkPad Extra Buttons:dmi:bvn*:bvr*:bd*:svnIBM*:pn*:pvr*
<snipped lines>
KEYBOARD_KEY_16=mute
Since this only affects udev >=196, possibly this is causing the difference. More investigation is needed, though.
x220t mute button
acpi_listen button/f20 F20 00000080 00000000 K
key scancode 0x5a 0xda
Is this still an issue? Shall we keep it open or can it be closed?
On my system, thinkpad-mutemic-acpi-hook
is not getting called because the ACPI event is button/f20 F20 00000080 00000000 K
(what @sniffer posted above).
However, the microphone mute button works correctly without thinkpad-mutemic
:
The light is turned on/off correctly based on the state of the microphone mute (even if I toggle mute entirely in software instead of pushing the button).
The button generates the XF86AudioMicMute
keysym, which most desktop environments handle correctly. (If not, you can bind the key to the correct command, such as using bindsym XF86AudioMicMute exec amixer -q -D pulse sset Capture toggle
in ~/.config/i3/config
for i3wm.)
@martin-ueding Does the your microphone mute button work correctly without thinkpad-mutemic
? If not, we should add another hook for the new ACPI event. If it does, we should consider removing thinkpad-mutemic
since the problem it was meant to solve now appears to be fixed.
My microphone-mute button does not work at all. My speaker-mute button works, though. I am not sure how much of the problem is Awesome WM with KMix to bind the keys or our suite of scripts :-/.
On my machine, there are no ACPI events when pressing the mute button, so
think-mutemic-acpi-hook
is never called. However, the mute button does issue keypress events (keycode 190) and GNOME 3.10 responds properly by muting the microphone. The indicator light integrated into the mute button still doesn't work, though.I assume the missing ACPI events are due to my more recent version of the thinkpad-acpi kernel module. I'll be interested to hear if
think-mutemic-acpi-hook
works properly with Ubuntu 13.10. I'm creating this issue so that I don't forget about it.