Bug 99682

Summary: Mouse clicks sometimes repeat
Product: Wayland Reporter: Nick Tenney <nick.tenney>
Component: libinputAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: medium CC: nick.tenney, peter.hutterer
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: Naga Mouse evemu output - 10 left clicks
Naga Keypad evemu output
Naga Keypad udevadm output
Naga Mouse udevadm output
libinput-list-devices output

Description Nick Tenney 2017-02-05 03:07:19 UTC
Created attachment 129341 [details]
Naga Mouse evemu output - 10 left clicks

I am running Archlinux using libinput 1.6.1 and have had issues with mouse clicks sometimes resulting in repeat clicks (i.e., clicking once can result in several clicks).  I tried this one two independent devices - one running wayland and another running xorg-server.  I verfied correct behavior (1 click = click event) on a Windows install.

It's a funny mouse, so there are two evemu and udevadm files (looks like event18 is the mouse, event19 is the numeric keypad on the side).  I for the event18 output, I left clicked 10 times. I believe there are click artifacts in the log.
Comment 1 Nick Tenney 2017-02-05 03:08:13 UTC
Created attachment 129342 [details]
Naga Keypad evemu output
Comment 2 Nick Tenney 2017-02-05 03:08:45 UTC
Created attachment 129343 [details]
Naga Keypad udevadm output
Comment 3 Nick Tenney 2017-02-05 03:09:15 UTC
Created attachment 129344 [details]
Naga Mouse udevadm output
Comment 4 Nick Tenney 2017-02-05 03:10:00 UTC
Created attachment 129345 [details]
libinput-list-devices output
Comment 5 Peter Hutterer 2017-02-07 00:43:51 UTC
tbh, this looks like a hw issue. There are 18 full clicks in the log you say should contain 10. Let's look at the timestamps of the first few:


E: 0.435950 0004 0004 589825	# EV_MSC / MSC_SCAN             589825
E: 0.435950 0001 0110 0001	# EV_KEY / BTN_LEFT             1
E: 0.435950 0000 0000 0000	# ------------ SYN_REPORT (0) ---------- +427ms
E: 0.469936 0004 0004 589825	# EV_MSC / MSC_SCAN             589825
E: 0.469936 0001 0110 0000	# EV_KEY / BTN_LEFT             0
E: 0.469936 0000 0000 0000	# ------------ SYN_REPORT (0) ---------- +34ms
E: 0.519991 0004 0004 589825	# EV_MSC / MSC_SCAN             589825
E: 0.519991 0001 0110 0001	# EV_KEY / BTN_LEFT             1
E: 0.519991 0000 0000 0000	# ------------ SYN_REPORT (0) ---------- +50ms
E: 0.528984 0004 0004 589825	# EV_MSC / MSC_SCAN             589825
E: 0.528984 0001 0110 0000	# EV_KEY / BTN_LEFT             0
E: 0.528984 0000 0000 0000	# ------------ SYN_REPORT (0) ---------- +9ms
E: 1.026952 0004 0004 589825	# EV_MSC / MSC_SCAN             589825
E: 1.026952 0001 0110 0001	# EV_KEY / BTN_LEFT             1
E: 1.026952 0000 0000 0000	# ------------ SYN_REPORT (0) ---------- +498ms

this reads as: button down, 34ms later button up and one more down up within
50/9 ms. That's incredibly fast. Attach a recording of a single click only
please so we can guess at what the device does. But either way, this seems
like a hardware issue. The Naga devices are configurable, are you sure this isn't configured to send double-clicks or something? or have a repeat-click firing? Did the windows install have the razer drivers installed at all?
Comment 6 Peter Hutterer 2017-02-13 23:30:14 UTC
ping?
Comment 7 Nick Tenney 2017-02-14 00:59:50 UTC
Thanks for the ping!  I am not surprised by the hardware failure, tbh.  I'm going to go ahead and close this from that perspective.  I did have drivers installed in Windows, and I wonder if the threshold for a "click" differs there.  If you're still curious, I can pull out the mouse and record a quick click too.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.