Arch Linux

yuvadm

Member

From: Tel Aviv-Jaffa, Israel

Registered: 2012-08-08

Posts: 103

Website

Volume keys stopped working on wireless Microsoft keyboard

For a while now I've been using a wireless Microsoft keyboard

$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech MX Master                      	id=10	[slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft® 2.4GHz Transceiver v9.0	id=12	[slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft® 2.4GHz Transceiver v9.0	id=14	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
    ↳ Logitech MX Master                      	id=15	[slave  keyboard (3)]
    ↳ Microsoft Microsoft® 2.4GHz Transceiver v9.0 (keys)	id=11	[slave  keyboard (3)]
    ↳ Microsoft Microsoft® 2.4GHz Transceiver v9.0	id=13	[slave  keyboard (3)]

A few days ago the special volume keys stopped working (play/pause, vol down, vol up, vol mute). Today I figured out those keys are the only ones on the keyboard, including other special keys, that are routed to a different input device than all the other keys (event7 instead of event5, in this case):

$ sudo libinput-debug-events
-event2 	DEVICE_ADDED     Power Button                      seat0 default group1 cap:k
-event3 	DEVICE_ADDED     Video Bus                         seat0 default group2 cap:k
-event1 	DEVICE_ADDED     Power Button                      seat0 default group3 cap:k
-event0 	DEVICE_ADDED     Sleep Button                      seat0 default group4 cap:k
-event4 	DEVICE_ADDED     Logitech MX Master                seat0 default group5 cap:kp left scroll-nat scroll-button
-event5 	DEVICE_ADDED     Microsoft Microsoft® 2.4GHz Transceiver v9.0 seat0 default group6 cap:k
-event6 	DEVICE_ADDED     Microsoft Microsoft® 2.4GHz Transceiver v9.0 seat0 default group6 cap:p left scroll-nat scroll-button
-event7 	DEVICE_ADDED     Microsoft Microsoft® 2.4GHz Transceiver v9.0 seat0 default group6 cap:kp scroll-nat calib
-event5 	KEYBOARD_KEY      +2.22s	KEY_A (30) pressed
a event5 	KEYBOARD_KEY      +2.36s	KEY_A (30) released
 event5 	KEYBOARD_KEY      +2.77s	KEY_B (48) pressed
b event5 	KEYBOARD_KEY      +2.90s	KEY_B (48) released
 event5 	KEYBOARD_KEY      +3.26s	KEY_C (46) pressed
c event5 	KEYBOARD_KEY      +3.41s	KEY_C (46) released
 event5 	KEYBOARD_KEY      +7.50s	KEY_LEFTMETA (125) pressed
 event5 	KEYBOARD_KEY      +7.50s	KEY_F21 (191) pressed
 event5 	KEYBOARD_KEY      +7.59s	KEY_LEFTMETA (125) released
 event5 	KEYBOARD_KEY      +7.59s	KEY_F21 (191) released
 event5 	KEYBOARD_KEY      +7.62s	KEY_LEFTMETA (125) pressed
 event5 	KEYBOARD_KEY      +7.62s	KEY_F21 (191) pressed
 event5 	KEYBOARD_KEY      +7.78s	KEY_LEFTMETA (125) released
 event5 	KEYBOARD_KEY      +7.78s	KEY_F21 (191) released
 event5 	KEYBOARD_KEY      +8.27s	KEY_LEFTCTRL (29) pressed
 event5 	KEYBOARD_KEY      +8.27s	KEY_LEFTMETA (125) pressed
 event5 	KEYBOARD_KEY      +8.27s	KEY_BACKSPACE (14) pressed
^H event5 	KEYBOARD_KEY      +8.40s	KEY_LEFTCTRL (29) released
 event5 	KEYBOARD_KEY      +8.40s	KEY_LEFTMETA (125) released
 event5 	KEYBOARD_KEY      +8.40s	KEY_BACKSPACE (14) released
-event7 	KEYBOARD_KEY     +10.64s	KEY_MUTE (113) pressed
 event7 	KEYBOARD_KEY     +10.79s	KEY_MUTE (113) released
 event7 	KEYBOARD_KEY     +11.01s	KEY_VOLUMEDOWN (114) pressed
 event7 	KEYBOARD_KEY     +11.22s	KEY_VOLUMEDOWN (114) released
 event7 	KEYBOARD_KEY     +11.49s	KEY_VOLUMEUP (115) pressed
 event7 	KEYBOARD_KEY     +11.59s	KEY_VOLUMEUP (115) released

Any idea what caused this change? And what do I need to change in order for the keys to register as they usually would? I usually use xbindkeys to bind them to alsa volume actions, if it matters.

Last edited by yuvadm (2016-10-21 11:27:37)