New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pointer speed "too fast" even if sensitivity and acceleration slowest #200
Comments
I've got a Chrombook fully converted to Debian(Chrome entirely removed) with the opposition problem due to a kernel issue: a very slow and unresponsive touchpad |
@lukefromdc Okay then you're not really commenting on the right bug. Try finding a bug that is relevant to your issue rather than trying to hijack an unrelated bug report. |
Anyways, the reason I came here is because it's 2019, this bug still exists and no one has even triaged this bug report yet. Mate defaults with the sensitivity and cursor speed set to minimum (at least on GhostBSD) and yet the cursor speed is way too fast. This makes the desktop virtually unusable because you touch the trackpad and the cursor acts like yuou've punched its newly born puppy and jumps all the way across the screen. |
We're encountering the same issue on Debian too, the mouse speed is usually too slow for some of our users. We've implemented the support "Device Accel Constant Deceleration" downstream to make our users able to decrease the mouse speed. Best regards, |
Hi MATE. 2.5 years from OP, and downstream means what exactly? :-) Don't worry others experience it do, I am currently posting from a Fedora 32 MATE install, and my mouse is annoyingly fast and impossible for pixel-level accuracy for blender and GIMP same as Debian. (yes it's a high-dpi gaming mouse) but MATE mouse setting screen is all the way down, and xinput does not show this mouse supports Device Accel Constant Deceleration. xinput --list-props 10 I tried manually specifying it, trying all possible combinations of --type & --format, but nothing seemed to work. Guess this value needs to be instantiated by the mouse driver first? Well anyway, searching around, I've found that some people need to use Coordinate Transformation Matrix, and that definitely works for me: xinput set-prop "USB Optical gaming mouse" "Coordinate Transformation Matrix" 0.20 0 0 0 0.20 0 0 0 1 Just saying. 5x slower and still being on the lowest setting in the GUI make it usable. I settled on 0.18 and then that gives me some control in the GUI like a normal user. If we can't do this from the MATE control panel, can we have a blurb pop up when people put the sliders all the way left they might need to investigate xinput solutions or something? A clue? It's a thought. Thanks! |
@Anaglyphic your workaround really helped, thank you! |
This suggests both minimum and maximum speeds could be made more extreme, plus some way to revert with only the keyboard in case you accidently get an uncontrollable mouse. |
Context
Some visual-impaired uses screen magnifier (as the Compiz built-in, ezoom) and have difficulties to move the mouse and fix a specific area of the screen. They expect to be able to reduce the mouse speed.
Expected behaviour
When the pointer speed is slow the speed of the mouse should be really slow
Actual behaviour
Even if the mouse speed is slow the mouse pointer speed stay fast.
Steps to reproduce the behaviour
To reduce the pointer speed I've used xinput as described in this thread : https://askubuntu.com/questions/688270/mouse-speed-too-fast
MATE general version
1.18
Package version
1.18.2-1
Linux Distribution
Debian sid
The text was updated successfully, but these errors were encountered: