Spurious mouse events cause double clicks

Bug #550047 reported by Leo Howell
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
xserver-xorg-input-evdev (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: xorg

[This seems to be the same as bug #27175, but since that was marked as fixed long ago I'm opening a new one]

Occasionally single clicks cause results that would only be expected from double clicks. For example:
- Click on a window title bar to focus the window occasionally causes it to maximize
- Click on a document in nautilus to select it occasionally opens the document
- Clicking on toolbar buttons in any app occasionally causes the button action to occur twice

On an updated fresh install of 10.4 beta 1 (xorg 1:7.5+3ubuntu1), with home directory preserved from a previous install of 9.10, where this problem did not occur.

The log from xev of this problem looks like this (from a single click):

ButtonPress event, serial 33, synthetic NO, window 0x4c00001,
    root 0x15d, subw 0x0, time 14769063, (80,82), root:(1819,659),
    state 0x0, button 1, same_screen YES

ButtonRelease event, serial 33, synthetic NO, window 0x4c00001,
    root 0x15d, subw 0x0, time 14769159, (80,82), root:(1819,659),
    state 0x100, button 1, same_screen YES

ButtonPress event, serial 33, synthetic NO, window 0x4c00001,
    root 0x15d, subw 0x0, time 14769167, (80,82), root:(1819,659),
    state 0x0, button 1, same_screen YES

ButtonRelease event, serial 33, synthetic NO, window 0x4c00001,
    root 0x15d, subw 0x0, time 14769175, (80,82), root:(1819,659),
    state 0x100, button 1, same_screen YES
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
DkmsStatus:
 nvidia-current, 195.36.15, 2.6.32-17-generic, x86_64: installed
 virtualbox-ose, 3.1.4, 2.6.32-17-generic, x86_64: installed
 virtualbox-ose, 3.1.4, 2.6.32-16-generic, x86_64: installed
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
MachineType: Gigabyte Technology Co., Ltd. GA-MA74GM-S2H
NonfreeKernelModules: nvidia
Package: xorg 1:7.5+3ubuntu1
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=96d841ba-99fe-454a-85ed-1f9af34c233c ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=ja_JP.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Tags: lucid lucid
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
dmi.bios.date: 02/01/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: GA-MA74GM-S2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd02/01/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GM-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GM-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA74GM-S2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-17-generic

Revision history for this message
Robert Hooker (sarvatt) wrote :

Please run apport-collect 550047 to attach the logs we need to this bug report. Since you mentioned you kept your old home directory, did you verify that this does also happen when you boot from a livecd?

Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Leo Howell (leo-lwh) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Leo Howell (leo-lwh) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : Dependencies.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : GdmLog.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : GdmLog1.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : GdmLog2.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : Lspci.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : Lsusb.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : PciDisplay.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : ProcModules.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : UdevDb.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : UdevLog.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : XorgConf.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : XorgLog.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : XorgLogOld.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : Xrandr.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : setxkbmap.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : xdpyinfo.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote : xkbcomp.txt

apport information

Revision history for this message
Leo Howell (leo-lwh) wrote :

I just tested with the 10.04 beta 1 live cd (without enabling the proprietary nvidia driver); the bug still occurs.

Revision history for this message
Robert Hooker (sarvatt) wrote :

Thanks for that, have you tried changing the double click timeout in system - preferences - mouse to see if you can get it to an acceptable behavior?

affects: xorg (Ubuntu) → xserver-xorg-input-evdev (Ubuntu)
Changed in xserver-xorg-input-evdev (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Leo Howell (leo-lwh) wrote :

Changing the double click timeout seemed to work as expected for actual double-clicks, but unfortunately it didn't stop single clicks as sometimes behaving as double (even if I leave several seconds between clicks).

Bryce Harrington (bryce)
tags: added: lucid
Revision history for this message
Nick Hlavacek (nick-nickspace) wrote :

Running xev I can see that holding down the left mouse button causes repeated click/release events for the duration of the hold. A single click is usually enough time for two clicks to register; holding the button down for one second leads to at least 10 click/release pairs. The problem is intermittent. The mouse is a standard Dell optical mouse.

tags: added: meerkat
Revision history for this message
Magosányi Árpád (mag-magwas) wrote :

Same problem here. An old HP mouse (could not figure out the type) sends mostly multiple buttonrelease events.
I have connected an additional Logitech M570 (restarted nothing, just plugged in), and that one does the same. Watching their behaviour in xev it seems that after connecting, the m570 is much more prone to erroneous behaviour. Actually it seemed that the "first" mouse behaves badly.
This machine is very old and not upgraded for a long time. I see that the last comment is 3 years old to this bug.
Maybe it is silently fixed already?

Revision history for this message
penalvch (penalvch) wrote :

Leo Howell, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-input-evdev REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xserver-xorg-input-evdev (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-input-evdev (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-input-evdev (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Paul Leopardi (paul-leopardi-iinet) wrote :

I tried to use apport-collect here, but it told me to use apport-bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.