Bug 28673

Summary: single mouse click interpreted as multiple clicks, especially when moving
Product: xorg Reporter: Antoine Martin <antoine>
Component: Input/MouseAssignee: Peter Hutterer <peter.hutterer>
Status: RESOLVED NOTOURBUG QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: antoine, bugs
Version: 7.4 (2008.09)   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Antoine Martin 2010-06-22 10:25:11 UTC 
Almost every click is interpreted as multiple clicks, especially when moving around.
I originally thought this might be related to a package upgrade, but I have since tested this mouse on 3 different computers and *all* exhibit the problem to some extent: Fedora 13 x86_64, Ubuntu 10.04 x86_64 and Ubuntu i386 (this last one less so for some reason)

I don't think that there is a hardware fault with the mouse since 3 different computers have similar problems but with different degrees of seriousness.

As reported before, doing a single clicks generally shows:
$ xev | grep Button
ButtonPress event, serial 35, synthetic NO, window 0x6200001,
ButtonRelease event, serial 35, synthetic NO, window 0x6200001,
ButtonPress event, serial 35, synthetic NO, window 0x6200001,

And if I move the mouse around whilst holding the button down it is even worse and generates dozens of clicks! (except on the third computer which will only generate a few)

I found some previous references to this problem, but no solution has worked for me:
http://linux.derkeiler.com/Mailing-Lists/Fedora/2009-01/msg00836.html
Suggested:
Option "AutoAddDevices" "off"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196711
Suggested:
Section "InputDevice"
 Identifier	"CorePointer"
 Driver	 "mouse"
EndSection

As requested, here is
$ xinput --list:
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ CorePointer                             	id=6	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ <default keyboard>                      	id=7	[slave  keyboard (3)]

Mouse is a "Sigma ONYX 8 button laser mouse" model SLATL01BK

Any help or workarounds would be much appreciated.
Comment 1 Peter Hutterer 2010-07-01 16:41:47 UTC 
what's the evtest output for this mouse? Does the kernel already emit multiple button events?
Comment 2 Raimar Sandner 2010-11-02 06:07:38 UTC 
I have the same problem. This is very annoying, although it doesn't happen very often at my system.

Here is the relevant evtest output:

$ sudo ./evtest /dev/input/event12 | grep LeftBtn
    Event code 272 (LeftBtn)
Event: time 1288700703.767367, type 1 (Key), code 272 (LeftBtn), value 1
Event: time 1288700709.607629, type 1 (Key), code 272 (LeftBtn), value 0
Event: time 1288700712.055717, type 1 (Key), code 272 (LeftBtn), value 1
Event: time 1288700720.784131, type 1 (Key), code 272 (LeftBtn), value 0
Event: time 1288700723.320214, type 1 (Key), code 272 (LeftBtn), value 1
Event: time 1288700731.848621, type 1 (Key), code 272 (LeftBtn), value 0
Event: time 1288700733.592708, type 1 (Key), code 272 (LeftBtn), value 1
Event: time 1288700734.496732, type 1 (Key), code 272 (LeftBtn), value 0
Event: time 1288700734.512719, type 1 (Key), code 272 (LeftBtn), value 1
Event: time 1288700737.688877, type 1 (Key), code 272 (LeftBtn), value 0

I pressed the left mouse button (value 1) and moved the mouse for several seconds, then released the mouse button (value 0). The first three times, there were no additional mouse button events. The fourth time, the bug is triggered: there is a button release event and a button press event within a few milliseconds (timestamps 1288700734.496732 and 1288700734.512719). But actually, the mouse button was pressed during this time.

Please let me know if I can help with any additional information.
Comment 3 Peter Hutterer 2010-11-02 18:24:15 UTC 
please file this bug with the kernel, there isn't much we can do.
if the kernel gives us erroneous data, we don't know that so we interpret the above input as several physical button presses.

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.