Mouse cursor jumping erratically + takes clicking action when not moved?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,634
Rep:
Mouse cursor jumping erratically + takes clicking action when not moved?
Hi all,
I recently installed SuSE 10.3 and now have intermittently the above error: the mouse cursor is jumping erratically all over the screen, when hitting the panel it even takes clicking action, all the while I'm not moving the mouse at all.
At some point in time it stops (faster, when I turn the mouse on its back or darken the red diode with my thumb) only to begin again some time later (or at once).
I got another mouse, same thing happens. This is from /var/log/messages:
Code:
Excerpts from /var/log/messages
…
Mar 9 18:17:13 linux kernel: psmouse.c: bad data from KBC - timeout
Mar 9 18:17:13 linux kernel: psmouse.c: bad data from KBC - timeout
Mar 9 18:17:13 linux kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Mar 9 18:17:14 linux kernel: psmouse.c: resync failed, issuing reconnect request
Mar 9 18:17:15 linux kernel: input: PS/2 Logitech Mouse as /class/input/input5
…
Mar 9 18:19:47 linux kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Mar 9 18:20:13 linux kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
…
Mar 9 18:21:02 linux kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Mar 9 18:22:01 linux syslog-ng[2115]: last message repeated 4 times
…
Feb 4 18:32:47 linux kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Feb 4 18:32:47 linux kernel: psmouse.c: resync failed, issuing reconnect request
Feb 4 18:32:48 linux kernel: input: ImPS/2 Generic Wheel Mouse as /class/input/input5
Can one change sensitivity in x.conf or something? Anybody any ideas?
Does the driver take parameters? Where would I find documentation?
Okay, I didn't find your remark to use YAST in time, I'll try that tonight.
<edit> The only difference I see in the xorg.conf lines is <<Option "Buttons" "9">> where I have 5. What kind of mouse do you use? I have a standard model with two buttons an a clickable wheel. </edit>
I see your config is the same as mine...notice the vendors name?
use root powers and copy and paste my mdv config into your /etc/X11/xorg.conf after making a backup of course....and assuming you know how to use a live cd to boot into that and rename your backup...the real conf file if my suggestion causes a crash.
IMHO, 9 buttons is too much.
my device was emulated but stable as I said in Virtualbox....if you are not familar with it...its worth having to test out iso images. You do not need to burn the iso image to a cdrw or dvdrw to test the distro.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,634
Original Poster
Rep:
Will do that tonight. Australia and Europe are somewhat out of sync concerning the time on the clock , it is 8:20 in the morning here and I'm at work. Thanks for the graphics btw.
I noticed the change to
Code:
Option "Protocol" "imps/2"
from
Code:
Option "Protocol" "explorerps/2"
Could it be that it is only this different protocol? I could test that after manual editing...
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,634
Original Poster
Rep:
Okay, I did it with YAST exactly as you suggested, but it didn't work, i.e. the error remained unchanged.
I had a look at /var/log/messages directly after the mouse threw a "fit" and it said there something like
Code:
Wheel Mouse at /isa006/... lost synchronization, throwing 3 bytes away
I'd interpret that as a problem in the data exchange between mouse and x-server which might be solved by using a different protocol. But which one? Or do you have different a explanation / suggestion?
Do you know where I could find a description of the possible protocols as used by the mouse?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.