You are not logged in.
Hi everyone,
I'm using a Logitech G602 mouse, which stores button mappings internally. For example, you can bind a mouse button to "CTRL+w", and the mouse will send a "CTRL" keydown event followed by a "w" keydown event.
These mappings have stopped working after a recent Arch upgrade, because the events are now injected in the wrong order. The following is from xev:
KeyPress event, serial 37, synthetic NO, window 0x7e00001,
root 0x497, subw 0x0, time 422379502, (69,47), root:(1260,786),
state 0x0, keycode 25 (keysym 0x77, w), same_screen YES,
XLookupString gives 1 bytes: (77) "w"
XmbLookupString gives 1 bytes: (77) "w"
XFilterEvent returns: False
KeyPress event, serial 37, synthetic NO, window 0x7e00001,
root 0x497, subw 0x0, time 422379502, (69,47), root:(1260,786),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
As you can see, the "w" key is down before the "CTRL", so the "CTRL+w" shortcut fails to work.
I have an older Arch installation from a few months ago, and the same mouse works fine there (xev says that "CTRL" is received before "w").
I'm using Xfce, and the 4.9.67-1-lts kernel. The issue is reproducible even with the latest non-LTS kernel.
Any advice would be much appreciated.
Last edited by Achelous (2017-12-15 19:03:02)
Offline
Fixed in libinput 1.9.4:
libinput 1.9.4 is now available. This fixes a regression introduced in 1.9.3 where some key events got lost or arrived out-of-order.
Offline