Problem :
Since my Manjaro Linux use libinput, the Trackball (Logitech M570) has a slow Mousepointer (Acclaratiton).
Adjusting it via KDE-GUI-Panel for mouse didn’t work, even like adjusting at cli via xinput.
Solution :
I found this thread, which suggest to create a hwdb-file to setup the right DPI for the mouse: https://bugzilla.redhat.com/show_bug.cgi?id=1217881#c8
This even not work, but point me to the right direction. I was confused, because If I enter xinput list, I got two entries:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Logitech M570 id=11 [slave pointer (2)]
⎜ ↳ Logitech M570 id=12 [slave pointer (2)]
So I thougt, maybe the first suggestion didn’t work at Manjaro (arch) Linux, because udev found to much entries for the name of the mouse.
So I go on to search how to replace the “name:” Parameter in this command and found this Page: https://github.com/arduino/dfu-utils-cross/blob/master/eudev-3.1.5/hwdb/70-mouse.hwdb
# if vid/pid is unavailable, use
# mouse:*:name:<name>:
# if name is unavailable, use
# mouse:<subsystem>:v<vid>p<pid>:*
#
# For example, the following 5 matches all match the same mouse:
# mouse:usb:v17efp6019:name:Lenovo Optical USB Mouse:
# mouse:usb:*:name:Lenovo Optical USB Mouse:
# mouse:usb:v17efp6019:*
# mouse:*:name:Lenovo Optical USB Mouse:
So I've done this, which work for me:
sudo /etc/udev/hwdb.d/99-m570.hwdb
# Logitech M570 trackball
mouse:usb:v046dp1028:name:*:
MOUSE_DPI=540@167
Then do:
sudo udevadm hwdb --update Then restart X.
Changing the Settings at the KDE-Mouse-GUI Setting-panel still seems to have no effect, but the mousepoister is faster then before.
Hope this will be fixed soon.
I’m a little embarrassed to post my solution, which I realized after lots of xinput commands, as other posts suggest:
- Step 1: Remove the ball
- Step 2: Clean the sensor
- Step 3: Clean everything else
- Step 4: Put the ball back in
This mouse is very prone to accumulate lots of dirt below the ball. Gently clean everything you can; what is causing slowness in your mouse may be very probably be dirt blocking the optical sensor from properly tracking the ball movements.
A little picture of my M580 for reference on how I left it for it to work for me
I hope this helps! Sorry for the totally un-nerdy answer