After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 762527 - Double-click will often be ignored if mouse was moved 1-2px during clicks
Double-click will often be ignored if mouse was moved 1-2px during clicks
Status: RESOLVED DUPLICATE of bug 748501
Product: nautilus
Classification: Core
Component: general
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-02-23 12:40 UTC by el
Modified: 2017-08-28 12:57 UTC
See Also:
GNOME target: ---
GNOME version: 3.15/3.16


Description el 2016-02-23 12:40:00 UTC 
When doing a fast double-click and the mouse jumps a tiny distance of 1px or 2px between the clicks, the double-click will often be ignored. (interestingly, when doing an intentionally slow double-click near the edge of the maximum detection time span while moving the mouse in between the clicks from one corner of the icon to the other, it will usually work..)

As a result, I have moderate trouble on my laptop with my trackpoint to double click on things, and on my desktop with my gaming mouse I'm pretty much unable to double-click anything unless I try to click really slow intentionally (and as a result I can barely navigate folders with the mouse in the standard configuration).
Comment 1 Carlos Soriano 2016-02-23 12:51:28 UTC 
In wayland or X?
Comment 2 el 2016-02-23 13:02:39 UTC 
X.org X server 1.17.4
Comment 3 el 2016-04-15 16:38:44 UTC 
This also seems to happen with touch and not only the mouse, which makes it very hard to click anything with touch unless the single-click mode is enabled (which I'm now using on every computer I have).
Comment 4 António Fernandes 2017-08-28 12:57:17 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 748501 ***