Bug 11833 - evdev needs mouse button debounce, many spurious up/down events
Summary: evdev needs mouse button debounce, many spurious up/down events
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/evdev (show other bugs)
Version: 7.2 (2007.02)
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Peter Hutterer
QA Contact: Xorg Project Team
URL: https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-03 12:38 UTC by Jonathan Briggs
Modified: 2019-11-15 15:32 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Jonathan Briggs 2007-08-03 12:38:44 UTC
This problem is partly the fault of my mouse, an older MX900 Bluetooth (part of a DiNovo set).  But, the problem does not show up (or not so as I notice it) on Windows or older Linuxes.

I get many double or triple mouse click events from a single click.  With xev I watched it, and most clicks are a single Down/Up, but then I get a Down/Up/Down/Up.  If I hold the button down and wiggle my finger a bit, I can get it to happen fairly often.

I did verify that Xorg is not reading two mouse devices.  I used the void driver to force /dev/mice not to load, and I verified it with lsof -p <xorg PID>

I think it is a slightly flaky momentary switch on the button.  

On a regular click, these events come *so* fast that a human being could not possible have done them.  So I recommend adding an option to evdev (milliseconds?) to ignore button events (keyboard events too?) that happen too closely together.
Comment 1 Peter Hutterer 2008-12-20 21:26:51 UTC
mass reassignment. Zephaniah isn't the maintainer anymore.
Comment 2 Peter Hutterer 2008-12-20 21:50:02 UTC
Bug is more than 12 months old, closing as WONTFIX. 

Please reopen if this is still an issue with the current release.
Comment 3 Connor Behan 2016-03-23 00:36:05 UTC
It's still an issue.
Comment 4 Peter Hutterer 2017-03-08 09:10:27 UTC
Basically: this won't get fixed because the cost of adding and maintaining the code forever is *a lot* higher than just replacing a buggy mouse, sorry.
Comment 5 Alex G. 2017-07-11 14:21:37 UTC
Hello, I think you really missed the point here. 

1. this is a really really annoying bug.
2. A lot of users are affected by this bug (I know at least 4 person around me) and http://blog.guntram.de/?p=16 points to many reports.
3. It's very hard to understand how to query google for this, even harder to come down here. (a normal user, won't be able to understand the problem).
4. Windows seems to do software debouncing so the mouse appears to work on windows but not ubuntu, thus apparently leaving the fault on ubuntu.
5. new mouse seems to be faulty and it's hard to know it before buying.
Comment 6 Yves-Gwenael Bourhis 2019-11-15 14:13:22 UTC
Please see here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/602809

The problem is getting worse now with new pointing devices, and even with https://lists.freedesktop.org/archives/wayland-devel/2017-October/035469.html which says:
"Pointer devices now have button debouncing automagically enabled.
Ghost button release/press events due to worn out or bad-quality switches
are transparently discarded and the device should just work."
New pointing devices still trigger multiple clicks. Especially new pointing devices.
The same pointing devices have strictly no issues whatsoever under Windows where they work like a complete charm.

Currently the only solution with linux is old pointing devices, and/or the electronic device from here:
https://askubuntu.com/questions/496131/set-mouse-debounce-time

This bug was opened in 2007 and 12 years after is still ignored.
Using Matt Whitlock's patch here:
http://lists.x.org/archives/xorg-devel/2012-August/033225.html
Worked like a charm for several years when doing this:
http://blog.guntram.de/?p=16
But it doesn't apply anymore to the new evdev versions.
I confirm it was marvellously working as long as the patch could be applied and I was compiling and using it with no issues.
Now I can't use it anymore with the new versions.

Could you please consider removing it from wontfix after those 12 years where strictly nothing worked to fix it apart from a patch which was mistakenly for bad reasons refused?

Thanks in advance.


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.