You are not logged in.
Hi!
Since I got my new mouse 2 days ago my keyboard randomly repeats the last key pressed until I physically disconnect and reconnect it.
Two days ago I got a new mouse after my old one died. The new mouse is a Logitech G300S, which because of the extra buttons it presents itself as a keyboard and a mouse to the OS.
I searched the all-mighty archlinux wiki for the mouse model, and I found this entry. Did everything in that page, added the disable script to /etc/X11/xinit/xinitrc.d/ as 10-disable-mouse-keyboard.sh and after booting I check with xinput and the keyboard device is disabled:
$ xinput list-props 10
Device 'Logitech G300s Optical Gaming Mouse Keyboard':
Device Enabled (193): 0
Coordinate Transformation Matrix (195): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Send Events Modes Available (312): 1, 0
libinput Send Events Mode Enabled (313): 0, 0
libinput Send Events Mode Enabled Default (314): 0, 0
Device Node (315): "/dev/input/event13"
Device Product ID (316): 1133, 49734Still, after doing all that the issue persists. I don't have much experience in debugging these kind of issues. I searched a bit and found the evtest package, I just ran it monitoring my keyboard until the issue occured.
Here is an excerpt of the output:
Event: time 1569492416.803492, -------------- SYN_REPORT ------------
Event: time 1569492416.874502, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70012
Event: time 1569492416.874502, type 1 (EV_KEY), code 24 (KEY_O), value 0
Event: time 1569492416.874502, -------------- SYN_REPORT ------------
Event: time 1569492417.001487, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70036
Event: time 1569492417.001487, type 1 (EV_KEY), code 51 (KEY_COMMA), value 1
Event: time 1569492417.001487, -------------- SYN_REPORT ------------
Event: time 1569492417.090551, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70036
Event: time 1569492417.090551, type 1 (EV_KEY), code 51 (KEY_COMMA), value 0
Event: time 1569492417.090551, -------------- SYN_REPORT ------------
Event: time 1569492417.091486, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7002c
Event: time 1569492417.091486, type 1 (EV_KEY), code 57 (KEY_SPACE), value 1
Event: time 1569492417.091486, -------------- SYN_REPORT ------------
Event: time 1569492417.144486, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7002c
Event: time 1569492417.144486, type 1 (EV_KEY), code 57 (KEY_SPACE), value 0
Event: time 1569492417.144486, -------------- SYN_REPORT ------------
Event: time 1569492417.172487, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70008
Event: time 1569492417.172487, type 1 (EV_KEY), code 18 (KEY_E), value 1
Event: time 1569492417.172487, -------------- SYN_REPORT ------------
Event: time 1569492417.440327, type 1 (EV_KEY), code 18 (KEY_E), value 2
Event: time 1569492417.440327, -------------- SYN_REPORT ------------
Event: time 1569492417.476971, type 1 (EV_KEY), code 18 (KEY_E), value 2
Event: time 1569492417.476971, -------------- SYN_REPORT ------------
Event: time 1569492417.513641, type 1 (EV_KEY), code 18 (KEY_E), value 2
Event: time 1569492417.513641, -------------- SYN_REPORT ------------
Event: time 1569492417.550309, type 1 (EV_KEY), code 18 (KEY_E), value 2
Event: time 1569492417.550309, -------------- SYN_REPORT ------------
Event: time 1569492417.586972, type 1 (EV_KEY), code 18 (KEY_E), value 2
Event: time 1569492417.586972, -------------- SYN_REPORT ------------
Event: time 1569492417.623644, type 1 (EV_KEY), code 18 (KEY_E), value 2
Event: time 1569492417.623644, -------------- SYN_REPORT ------------
Event: time 1569492417.660314, type 1 (EV_KEY), code 18 (KEY_E), value 2
Event: time 1569492417.660314, -------------- SYN_REPORT ------------
Event: time 1569492417.696971, type 1 (EV_KEY), code 18 (KEY_E), value 2This goes on until I disconnect the keyboard.
Something that is quite curious is that it seems to happen with some keys more than with others, I've seen it happen a lot more with Control, E and M than with any other key. It seems to happen a lot when I do Control chords.
How should I go about debugging this issue?
Linux Pleiades 5.3.1-arch1-1-ARCH #1 SMP PREEMPT Sat Sep 21 11:33:49 UTC 2019 x86_64 GNU/LinuxOffline