https://bugzilla.redhat.com/show_bug.cgi?id=1483629
--- Comment #7 from Peter Rathlev <peter(a)rathlev.dk> ---
Thanks for the pointers!
At least for me it is not related to any kind of scrolling. In Kerbal Space
Program the pointer behaves exactly like the middle mouse button was never
pressed, until release, at which point it very very briefly acts as if pressed.
I tried "libinput debug-events" and it seems like libinput actually knows when
the "pressed" event arrives, but it doesn't print the event to the terminal
before the relase event has arrived. So the timestamp relative from process
start in third column displays the correct time, but the output line saying
this doesn't come until later.
The following is an example where I press the mousebuttons 1, 2, 3 in turn,
first doing a short-ish click and afterwards holding each button for a few
seconds (newlines inserted for readability):
# unbuffer libinput debug-events --device=/dev/input/event6 | ts '[%Y-%m-%d
%H:%M:%.S]'
[2017-11-14 21:40:12.359188] -event6 DEVICE_ADDED TPPS/2 IBM TrackPoint
seat0 default group1 cap:p left scroll-nat scroll-button
[2017-11-14 21:40:14.064402] event6 POINTER_BUTTON +1.71s BTN_LEFT
(272) pressed, seat count: 1
[2017-11-14 21:40:14.173700] event6 POINTER_BUTTON +1.82s BTN_LEFT
(272) released, seat count: 0
[2017-11-14 21:40:14.848094] event6 POINTER_BUTTON +2.39s BTN_MIDDLE
(274) pressed, seat count: 1
[2017-11-14 21:40:14.848271] event6 POINTER_BUTTON +2.50s BTN_MIDDLE
(274) released, seat count: 0
[2017-11-14 21:40:15.502475] event6 POINTER_BUTTON +3.15s BTN_RIGHT
(273) pressed, seat count: 1
[2017-11-14 21:40:15.591440] event6 POINTER_BUTTON +3.24s BTN_RIGHT
(273) released, seat count: 0
[2017-11-14 21:40:18.858315] event6 POINTER_BUTTON +6.51s BTN_LEFT
(272) pressed, seat count: 1
[2017-11-14 21:40:21.432588] event6 POINTER_BUTTON +9.08s BTN_LEFT
(272) released, seat count: 0
[2017-11-14 21:40:25.972962] event6 POINTER_BUTTON +10.82s BTN_MIDDLE
(274) pressed, seat count: 1
[2017-11-14 21:40:25.973145] event6 POINTER_BUTTON +13.62s BTN_MIDDLE
(274) released, seat count: 0
[2017-11-14 21:40:28.991058] event6 POINTER_BUTTON +16.64s BTN_RIGHT
(273) pressed, seat count: 1
[2017-11-14 21:40:32.251229] event6 POINTER_BUTTON +19.90s BTN_RIGHT
(273) released, seat count: 0
As you can see there are pressed/released events at +10.82s and +13.62s
respectively, but the output lines (per ts stamp) appear practically
simultaneously.
So I wonder, why does libinput seem to hold on to the "pressed" event for the
middle mouse button? My guess is that this is what makes both Blender and
Kerbal Space Program seem like the button isn't working.
--
You are receiving this mail because:
You are on the CC list for the bug.