linux-kernel - Re: 2.6.24: false double-clicks from USB mouse

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 02 Dec 2007 13:17:43 -0500
From:	Mark Lord <lkml@....ca>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	rubini@...ion.unipv.it, linux-input@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Jeff Garzik <jeff@...zik.org>
Subject: Re: 2.6.24:  false double-clicks from USB mouse

Jiri Kosina wrote:
> On Sun, 2 Dec 2007, Mark Lord wrote:
> 
>>> Single-clicking on things with 2.6.24 very frequently gives a 
>>> "double-click". This does not happen with 2.6.23.8. I wonder what 
>>> broke it? I've grabbed mousedev.c from 2.6.23 and inserted that in 
>>> place of the updated 2.6.24 source, but no change.  So it's not that 
>>> file.
>> Mmm.. reverting the entire drivers/hid directory to that from 2.6.23
>> seems to have fixed the problem, so we now know it's in there somewhere.
...

Mmmm.. an update here:

Reverting the drivers/hid directory does seem to improve behaviour.

But right now I have a "make -j4" happening in the background
and the mouse is ever so erratic again, despite the drivers/hid reversion.

So it's a timing thing, somewhere.
Maybe a scheduling thing?

Jiri:  I know nothing about how mouse clicks are interpreted,
or even *where* or *how* double-click detection happens.
Until this started happening, I didn't even know which module
was the driver for my mouse (it's usbhid).

Can you give a short tutorial, to help us understand possible causes ?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/