Hello all you good people,
My mouse is moving too fast. It is a simple Crystal White Mouse bij Logitech, nothing fancy. I tried setting DPI in the hwdb of udev. But it seems like it only works for a few seconds, and then the mouse is fast again. Setting accelaration to 0 also does not help.
I have no idea where the DPI is set. evdev is not present on this system.
My distro is ExeGnu.
Any ideas?
Eric-Jan
Anno domini 2019 Tue, 10 Dec 12:26:24 +0100 Internal Affairs scripsit:
Hello all you good people,
My mouse is moving too fast. It is a simple Crystal White Mouse bij Logitech, nothing fancy. I tried setting DPI in the hwdb of udev. But it seems like it only works for a few seconds, and then the mouse is fast again. Setting accelaration to 0 also does not help.
I have no idea where the DPI is set. evdev is not present on this system.
My distro is ExeGnu.
Any ideas?
Got biten by the same thing ~ a year ago, thinkpad touchpoint was affected. I came up with this solution (put it into your .xsession or .xinitrc or whatever thingie you use for autostart after session load):
# Acceleration of Touchpoint :-) # https://wiki.archlinux.org/index.php/Mouse_acceleration ( sleep 5 xinput --set-prop 'TPPS/2 IBM TrackPoint' 'libinput Accel Speed' -0.125 ) &
Nik
Eric-Jan
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Dr. Nikolaus Klepp wrote:
Got biten by the same thing ~ a year ago, thinkpad touchpoint was affected. I came up with this solution (put it into your .xsession or .xinitrc or whatever thingie you use for autostart after session load):
# Acceleration of Touchpoint :-) # https://wiki.archlinux.org/index.php/Mouse_acceleration ( sleep 5 xinput --set-prop 'TPPS/2 IBM TrackPoint' 'libinput Accel Speed' -0.125 ) &
Nik
Didn't the native TDE mouse acceleration setting work?
Anno domini 2019 Tue, 10 Dec 20:49:15 +0100 deloptes scripsit:
Dr. Nikolaus Klepp wrote:
Got biten by the same thing ~ a year ago, thinkpad touchpoint was affected. I came up with this solution (put it into your .xsession or .xinitrc or whatever thingie you use for autostart after session load):
# Acceleration of Touchpoint :-) # https://wiki.archlinux.org/index.php/Mouse_acceleration ( sleep 5 xinput --set-prop 'TPPS/2 IBM TrackPoint' 'libinput Accel Speed' -0.125 ) &
Nik
Didn't the native TDE mouse acceleration setting work?
The behaviour of Xorg changed after an update. Before TDE mouse acceleration worked as expected, allowing the mouse to slow. After the update the mouse acceleration cannot be turned off. (No, I won't blame the fine guys on freedesktop.org for breaking things depending on air pressure - it's just their job)
Nik
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Dr. Nikolaus Klepp wrote:
The behaviour of Xorg changed after an update. Before TDE mouse acceleration worked as expected, allowing the mouse to slow. After the update the mouse acceleration cannot be turned off. (No, I won't blame the fine guys on freedesktop.org for breaking things depending on air pressure
- it's just their job)
OK, but this means that for some mice the controls in TDE have no effect - correct?
I use a Benq mouse I bought in 2006 - seems a great hardware - never had problem with acceleration described - even after latest upgrade to buster.
However I have experienced odd things with cheap mouse and stupid KVM switch - like sticky keys - mouse not moving - strange messages about USB in the syslog etc.
Never mind - the thing is - the function in TDE should set the acceleration the way you do it in .xsetting, but I do not see an option to set for specific hardware.
I would file a request to update this in future major release.
Anno domini 2019 Tue, 10 Dec 21:31:51 +0100 deloptes scripsit:
Dr. Nikolaus Klepp wrote:
The behaviour of Xorg changed after an update. Before TDE mouse acceleration worked as expected, allowing the mouse to slow. After the update the mouse acceleration cannot be turned off. (No, I won't blame the fine guys on freedesktop.org for breaking things depending on air pressure
- it's just their job)
OK, but this means that for some mice the controls in TDE have no effect - correct?
Not exactly. I can change settings via TDE, but the effect has changed: Previously I could disable acceleration for my touchpoint, nowadays that does not work any more. For a touchpoint the model is e.g.:
dx_screen = dx_touchpoint * (a_driver + a_TDE) + dx_touchpoint ^ (b_driver + b_TDE)
Now "a_driver" and "b_driver" have changed (bigger as before) and the accepted values for "a_TDE" and "b_TDE" have change to > 0. So that's a problem TDE won't be able to fix :(
The negative acceleration value for libinput that I came up with is just a hotfix/hack, it does not restore old behaviour but is better than what I had without.
Oh, and it only affects the touchpoint (have I written "touchpad" earlier? ooops....)
Nik
I use a Benq mouse I bought in 2006 - seems a great hardware - never had problem with acceleration described - even after latest upgrade to buster.
However I have experienced odd things with cheap mouse and stupid KVM switch - like sticky keys - mouse not moving - strange messages about USB in the syslog etc.
Never mind - the thing is - the function in TDE should set the acceleration the way you do it in .xsetting, but I do not see an option to set for specific hardware.
I would file a request to update this in future major release.
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 12/11/2019 03:14 AM, Dr. Nikolaus Klepp wrote:
Not exactly. I can change settings via TDE, but the effect has changed: Previously I could disable acceleration for my touchpoint, nowadays that does not work any more. For a touchpoint the model is e.g.:
dx_screen = dx_touchpoint * (a_driver + a_TDE) + dx_touchpoint ^ (b_driver
- b_TDE)
Now "a_driver" and "b_driver" have changed (bigger as before) and the accepted values for "a_TDE" and "b_TDE" have change to > 0. So that's a problem TDE won't be able to fix :(
The negative acceleration value for libinput that I came up with is just a hotfix/hack, it does not restore old behaviour but is better than what I had without.
Oh, and it only affects the touchpoint (have I written "touchpad" earlier? ooops....)
Nik
Can also be the result of the underlying libinput/xinput changing. libinput for Wayland is appearing more and more there are some growing pains. Here are a few references for mouse acceleration and libinput (and xinput and xset)
https://wiki.archlinux.org/index.php/Mouse_acceleration
https://wiki.archlinux.org/index.php/Libinput
-
David C. Rankin -
deloptes -
Dr. Nikolaus Klepp -
Internal Affairs