Keeping usb mouse buttons pressed results in repeated ButtonPress events [regression]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
xorg (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
xserver-xorg-input-evdev (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: xserver-
I just updated a 7.10 installation to 8.04 and I tried both workarounds described in bug #173833 (placing 10-x11-input.fdi in /etc/hal/policy/ and manually setting the path to the device special file) to make it work.
With either one of them the mouse works, sort of. The problem is that if I keep a mouse button pressed it repeatedly generates ButtonPress events until I release it.
This makes the system almost unusable as most (all?) programs interpret these repeated ButtonPress-es as multiple clicks and thus:
* when I drag windows they maximize, then minimize maximize again, etc
* when I drag nautilus file or folders icons I instead draw fancy frames (the area-selection boxes)
* when I select something if I am not quick I instead double click it
* I cannot select stuff in xterm (the selection keeps resetting as I drag the mouse)
These are only examples of the many, many problems this bug causes: almost nothing is usable. Please also note that on the console gpm works correctly.
I'm attaching the relevant part of an xev log (but I don't think it wolud really help): I obtained it by pressing the left mouse button, waiting a handful of seconds and then releasing it.
I'm using a MightyMouse but it doesn't seem specific to this mouse (see my comment #2 below)
Finally note that it worked correctly with 7.10 and thus this is a regression.
Changed in xserver-xorg-input-evdev (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: hardy |
After further investigation I found that it is not Mighty Mouse specific but may happen with any USB mouse using the evdev driver (I'll change the description) and that even Mark Lord himself was hit:
http:// kerneltrap. org/mailarchive /linux- kernel/ 2007/12/ 2/468128
alas no suggestion nor conclusion about it, except that it might be specific to linux kernel 2.6.24. What's worse: a reboot solved the issue for Mark Lord but for me it doesn't :(