On 3/22/23 2:06 AM, Dr. Nikolaus Klepp via tde-users wrote:
Try using "xinput" (you'll most likely
have to install it first), then identify yout mouse device:
$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Kensington Expert Mouse id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ Cherry GmbH CHERRY Corded Device id=8 [slave keyboard (3)]
↳ Cherry GmbH CHERRY Corded Device id=9 [slave keyboard (3)]
Then look at the 'Coordinate Transformation Matrix' - you'll want to keep it
for later - the last Value is the "speed":
$ xinput list-props 'Kensington Expert Mouse' | grep 'Coordinate
Transformation Matrix'
Coordinate Transformation Matrix (164): 1.000000, 0.000000, 0.000000, 0.000000,
1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Then decrease speed by increasing the last value; e.g. make it 1/2 speed:
xinput set-prop 'Kensington Expert Mouse' 'Coordinate Transformation
Matrix' 1 0 0 0 1 0 0 0 2
When you are happy put it into your .xsessionrc or .xinitrc
Please note that this affects "speed", not "acdceleration".
YOu'll find for knobs to tur when you look at the acceleration properties:
$ xinput list-props 'Kensington Expert Mouse' | grep -i acce
libinput Accel Speed (314): 0.000000
libinput Accel Speed Default (315): 0.000000
libinput Accel Profiles Available (316): 1, 1
libinput Accel Profile Enabled (317): 1, 0
libinput Accel Profile Enabled Default (318): 1, 0
Nik
Thank you for replying, but jumping through such hoops is a bit silly in
this day and age, especially when there are no mouse pointer speed
problems in any other DE. :(