Cursor jumps while writing

[Brutanas]

Hello!
I am using FreeBSD-14.3 on a HP envy laptop with mate desktop and I am happy with it in general.
But since the beginning there is a thing that is annoying... when I am writing text (and it already happened while I am writing this text) the cursor jumps to another part of the text. It seams that the faster I write, the more frequently it happens.
I am almost 100% sure that it has nothing to do with the mouse pad, since I have been very careful being sure that my hands are far from it.
Does anyone has the same problem and knows how to solve it ?

Thank you!

 

[tingo]

some laptops can turn off the mousepad (using a key combination or a press on a specific point of the mousepad). If yours can do it, try to turn off the mousepad. In my experience, it is always the mousepad when the cursor moves.

 

[vmisev]

IDK if it is related, but you could try with keyrate= settings in rc.conf(5)

 keyrate         (str)   The   keyboard  repeat  speed.   Set  to  "slow", 
                 "normal", "fast" or "NO" if the default behavior  is  de- 
                 sired.

Or, you can try what tingo suggested. If there is no Fn-this-that way to disable it externally, you can try with xinput list to find your touchpad's device ID, then xinput list-props <your_dev_id>, then xinput set-prop <your_dev_id> <prop_id> 0 to disable it.

 

[drhowarddrfine]

EDIT: Ignore this. Replacing the mouse fixed my issue.

I am almost 100% sure that it has nothing to do with the mouse pad

Maybe unrelated but I thought I'd mention it. Since updating to 14.3-RELEASE, I've had an issue with the mouse pointer freezing in its position occasionally. I have to unplug and replug in the mouse to get it working again. (I want to say that even rebooting didn't fix it.)

Haven't had a chance to do any investigating but, since this happened on the same version, I wonder.

 

[vmisev]

Maybe unrelated but I thought I'd mention it. Since updating to 14.3-RELEASE, I've had an issue with the mouse pointer freezing in its position occasionally. I have to unplug and replug in the mouse to get it working again. (I want to say that even rebooting didn't fix it.)

Haven't had a chance to do any investigating but, since this happened on the same version, I wonder.

With or without ums_load="YES"?

 

[drhowarddrfine]

EDIT: Ignore this. Replacing my mouse fixed the issue.

With or without ums_load="YES"?

I would assume without but I forgot to mention that this is on a desktop computer and my mouse is the same one I've had for god knows how long. It's not a usb mouse but a PS2 mouse plugged into an old PS2 to USB converter.

Why do I use such an old thing? Because I'm cheap frugal.

 

[vmisev]

I would assume without but I forgot to mention that this is on a desktop computer and my mouse is the same one I've had for god knows how long. It's not a usb mouse but a PS2 mouse plugged into an old PS2 to USB converter.

Why do I use such an old thing? Because I'm cheap frugal.

If it's plugged into usb port, regardless of adapter, from OS perspective this should be an USB mouse.

Try to add ums_load="YES" in /boot/loader.conf, and comment out in /etc/rc.conf #moused_port=/dev/psmo0 (if you have that line), and leave just moused_enable="YES".

There is maybe some miscommunication going on between mouse, adapter and USB port, but that would be above me to solve. Plese see Thread 88823 and Thread 93764 for some more info.

 

[Brutanas]

IDK if it is related, but you could try with keyrate= settings in rc.conf(5)

 keyrate         (str)   The   keyboard  repeat  speed.   Set  to  "slow",
                 "normal", "fast" or "NO" if the default behavior  is  de-
                 sired.

Or, you can try what tingo suggested. If there is no Fn-this-that way to disable it externally, you can try with xinput list to find your touchpad's device ID, then xinput list-props <your_dev_id>, then xinput set-prop <your_dev_id> <prop_id> 0 to disable it.

Well... it seams that starting /usr/local/bin/syndaemon -i 1.0 -d -K solves the issue. At least when I run it manually after mate session started it seams to work. Now i am trying to start it in .xinitrc, but it does not start. How can I make it running. I am starting X with startx.

 

[vmisev]

Well... it seams that starting /usr/local/bin/syndaemon -i 1.0 -d -K solves the issue. At least when I run it manually after mate session started it seams to work. Now i am trying to start it in .xinitrc, but it does not start. How can I make it running. I am starting X with startx.

Thanks for the update and for posting your solution, I'm glad that it worked! TBH x11-drivers/xf86-input-synaptics didn't even cross my mind.