https://bugs.freedesktop.org/show_bug.cgi?id=104415
Peter Hutterer <peter.hutte...@who-t.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
--- Comment #5 from Peter Hutterer <peter.hutte...@who-t.net> ---
Ok, the issue here is the new button debouncing code. The event sequence shows
this for the second button press:
E: 0.135988 0004 0004 589825 # EV_MSC / MSC_SCAN 589825
E: 0.135988 0001 0110 0001 # EV_KEY / BTN_LEFT 1
E: 0.135988 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +8ms
E: 0.145980 0004 0004 589825 # EV_MSC / MSC_SCAN 589825
E: 0.145980 0001 0110 0000 # EV_KEY / BTN_LEFT 0
E: 0.145980 0000 0000 0000 # ------------ SYN_REPORT (0) ---------- +10ms
i.e. the device pretends the button was pressed 8ms after releasing it and
released 10ms after pressing it. This is too short a timeout for real-world
button clicking and is usually a sign of broken buttons. Because it is pressed
and released within the timeouts the button event is discarded (you should have
a message in the log warning you about this).
I can't think of a good way to fix this but I guess not debouncing of this set
of devices is a workaround.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
