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:Can one change sensitivity in x.conf or something? Anybody any ideas?

I have a opensuse 10.3 in virtualbox at the moment.

1) I am booting into kde.

2) suse icon/tab to computer/admin settings....input root passws/ gets you to mouse which you can check and test and change.

3) what does your mouse bit in /etc/X11/xorg.conf say?

my Mdv xorg section is

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/mouse"
EndSection

my opensuse is

Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Buttons" "9"
Option "Device" "/dev/input/mice"
Option "Name" "ImExPS/2 Generic Explorer Mouse"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
EndSection

I'll look this evening and be back tomorrow with my xorg.conf and also check the KDE settings for the mouse parameters.

its not kde settings that i refer to

its

click on the suse (start) button....bottom left hand icon....you are going into yast.

Good morning.

Here is my xorg.conf: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>

Try another mouse - they usually do that to me when they are about to die.

Did that already...

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.

anyhow give that a try and see what happens.

I just noticed another difference.

Your SuSEMy SuSE:That of any significance?

yeah its more basic....so try this in stages....
1) cp /etc/X11/xorg.conf /etc/X11/xorg.jl

(if below fails you need to use a live cd...to mount your / partition then rename that jl file back to xorg.conf

2) then go into yast with admin root powers and change mouse to basic 2 button one wheel mouse

http://h1.ripway.com/aus9/jl/yast1.png
http://h1.ripway.com/aus9/jl/yast2.png
http://h1.ripway.com/aus9/jl/yast3.png
http://h1.ripway.com/aus9/jl/yast4.png

3) note the last one....I could not do....as I was running an emulation so it would have affected my host computer.

it is up to you to confirm it is going to be stable....but on reboot for me....it was

4) before rebooting check your new xorg is this pls

Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Device" "/dev/input/mice"
Option "Name" "IMPS/2"
Option "Protocol" "imps/2"
Option "Vendor" "PS/2-Mouse"
Option "ZAxisMapping" "4 5"
EndSection

you may note we are going from your Name" "ImPS/2 Generic Wheel Mouse to a even more basic wheel mouse.

cheerio

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 tofrom Could it be that it is only this different protocol? I could test that after manual editing...

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 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?

try this post instead and the next

http://www.linuxquestions.org/questi...64#post1881264

try this post instead and the next

http://www.linuxquestions.org/questi...64#post1881264