X.org/kde 3.3: mouse gets "stuck" at the left of the screen

stefan_nicolau · 07-25-2005, 01:43 PM

I am using Debian Sid, and, recently, I have experienced a quite strange problem:

Once in a while, the mouse will get "stuck" at the left of the screen, meaning that whenever I exceed the pointer threshold defined in the kde control panel, the mouse will "teleport" to the left of the screen.
This happens wether I exceed the threshold by moving horizontally or vertically, but, in either case, the mouse only "teleports" horizontally.
I can move the mouse fine, as long as I don't exceed the threshold.
The issue is "fixed" when I leave the current X session. (either ctrl-alt-backspace or Kmenu->logout)

The only extra info I can provide is:
A) I did not experience this problem before X.org.
B) This seems to happen when the system is under heavy load.
C) The two above might very well be coincidences.
D) This is definitely not a hardware problem. I have tried several mice.

Moloko · 07-26-2005, 05:40 PM

Is the new xorg.conf the same as the previous XFree86Config4? Does your pet have more than two buttons etc?

stefan_nicolau · 07-27-2005, 03:05 AM

Quote:

Is the new xorg.conf the same as the previous XFree86Config4?

Yes, the syntax is the same, I use /dev/input/mice with the ExplorerPS/2 protocol, which should be provided by the kernel. I tried plugging the mouse on usb instead of PS/2, but it did not solve the problem. (Probably meaning that this is not a kernel/hardware issue, and that /dev/input/mice works fine. The fact that the issue dissapears upon X restart further proves this.)

Quote:

Does your pet have more than two buttons etc?

Yes, I use imwheel and xmodmap.

helmut_hed · 08-20-2005, 02:28 AM

Some users of PCTel modem drivers have been experiencing this issue on Fedora Core 4, although it's usually associated with weird colored/corrupted lines of text in terminal windows as well. Have you seen any such problems?

I would be interested to know what your version of xorg-x11 is, also, in case that's related.

Thanks and regards,
Jeff Trull
(helping out with PCTel drivers)

helmut_hed · 09-26-2005, 01:18 PM

Followup: a similar problem with the PCTel modem driver has been fixed and was due to corrupted floating point state caused by an incomplete register save procedure. Do you have any "unusual" drivers or interrupt handlers?

Regards,
Jeff
PS: You can see if this is your problem by running the following C program, which will accelerate the failures (thanks, OpenBSD!):

http://anoncvs.openbsd.lt/cgi-bin/vi...viewcvs-markup