On Tue, Nov 27, 2018 at 12:23 AM Peter Hutterer <peter.hutterer(a)who-t.net>
wrote:
this means the data itself is generated by the device, value 2 is
the
kernel's signal that a key is repeating and there doesn't seem to be a
release event. so the userspace layer (xkb) is going to repeat too
(independently on the kernel because we ignore value 2 events).
if you're on F29 with libinput >= 1.12.3, you can work around this for now
with this quirk:
$> cat /etc/libinput/local-overrides.quirks
[roccat autorepeat]
MatchName=ROCCAT ROCCAT Vulcan 120 AIMO
MatchUdevTag=keyboard
AttrEventCodeDisable=KEY_F15
This will simply ignore that specific key, so at least you can use your
machine until the root of the issue is found. Obviously that won't work
well
if you disable KEY_A or any other actually useful key...
> How should I continue? Should I place an bug report but to upstream or
> Fedora's own bugzilla?
either will do, I CC'd benjamin in case he wants it somewhere specific.
Make
sure you do attach the hid-recorder output for that device.
Cheers,
Peter
Peter,
thank you very much for hint to use hid-recorder, this tool is new to me.
Much easier to comprehend than usbmon / wireshark captures. I made bug
report on Fedora's bugzila, I'm more familiar with it:
https://bugzilla.redhat.com/show_bug.cgi?id=1653841
Br,
Juha