When changing properties of the mouse by using xset m, the mouse gets stuck and can not be moved, or it can be moved only horizontally/vertically. This bug is reproducible in any DE or WM, or even bare X. Steps to Reproduce: 1. Start bare X and an xterm from a console by "X & ; sleep 10 && xterm -display :0 &" 2. Change to vt7 and run "xset m 1/2 0". If mouse doesn't get stuck, then try to change the mouse setting back to default by running "xset m 2/1 4". Now, mouse gets stuck and can not be moved arbitrarily. What happens is that the mouse either can not be moved at all or it can be only horizontally or vertically. I have three mice on my T61 laptop (the touchpad, the trackpoint, and an external USB mouse). Usually the touchpad is the first to be unresponsive to finger movements (unresponsive in the sense that the mouse pointer does not move on the screen), and then the external mouse, and then the trackpoint. If the current pointer device is still working just give a couple more "xset m" commands, and it will stop moving the pointer too. This is with nvidia drivers, xorg-server-1.7.7. This bug was also present in xorg-server-1.7.6. At the time I had filed a bug report (a couple of months ago) on gentoo bugzilla [ http://bugs.gentoo.org/show_bug.cgi?id=321501 ], this bug was reproduced in xorg-1.8 by a different person on IRC, and I personally could reproduce it on a ubuntu-10.04 default x86 installation (which was running xorg-server-1.7.6).
Happens for me too with xorg-server 1.9.2 and xf86-input-evdev 2.5.0.
Is this a regression?
(In reply to comment #2) > Is this a regression? It is hard to remember exactly, given that the bug was filed so long ago. I have had the external USB mouse since 2008 and I have always had to run 'xset m' on login to reduce its sensitivity. Only around 2010, did I get these weird behavior. So, I believe it is a regression, probably introduced towards the end of 2009 or later. I can not be sure of the exact timescale since Gentoo *stable* X is usually several months behind the actual releases of X.
Thanks. Looking at Gentoo's ChangeLog, that sounds like it probably worked in 1.5.x and broke in either 1.6 or 1.7 ...
This is a mass change of bugs. Bugs assigned to me that haven't been updated in the last 3 years are closed as WONTFIX, because, well, let's at least be honest about it. Please do not re-open unless you have a really good reason to do so (e.g. you're fixing it yourself). If it hasn't been fixed in the last 3 years, it probably won't be fixed anytime soon either. Sorry.
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.