Bug 323295 - Mouse settings for pointer and threshold have no effect.
Summary: Mouse settings for pointer and threshold have no effect.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_mouse (show other bugs)
Version: 1.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-08 18:34 UTC by Marc Chamberlin
Modified: 2024-03-25 01:40 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Chamberlin 2013-08-08 18:34:19 UTC
I fiddled with the mouse pointer and threshold settings under the Advance tab for configuring the mouse and actually tried large ranges of numbers/combinations for each. There was NO effect on the behavior of the cursor in relation to the amount of mouse movement.  I dunno if this makes any difference but I am using an ASUS optical USB mouse.

What I want is that initially I want to move the mouse a large distance and only have a small amount of cursor movement. This is so as to be able to point at  things easily, like window  borders which are only 1 or 2 pixels wide and difficult to point at (very bad design IMHO!) After moving the mouse a ways, THEN I want the acceleration to kick in.

Reproducible: Always

Steps to Reproduce:
1. Open Configure Desktop
2. Select Input Devices
3. Select Mouse
4. Select Advance tab
5. Change values for Pointer Acceleration and Pointer Threshold
Actual Results:  
No change in behavior of cursor movement in relationship to mouse movement.

Expected Results:  
I expect to see a difference in the relationship of how far the cursor moves in response to various amount of mouse movement.
Comment 1 LTHR 2013-09-05 10:30:08 UTC
The mouse issue is confirmed with gentoo/amd64/kde 4.10.5 and MX518 mouse
Luckily this mouse has a hardware acceleration buttons. 

It's not the only input issue. There are similar annoying problem with keyboard repeat rate delay. 

1. The keyboard repeat rate cannot be turned off.
2. The delay higher than 400 are ignored. 
3. With preemptive kernel when system is busy there are many keyboard repeats. 

These problems never happened with 4.9.5 
I wonder what was the reason of rebuilding the stable drivers.
Comment 2 Andrew Crouthamel 2018-11-11 04:24:14 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:47:56 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Alan Prescott 2020-06-07 09:08:36 UTC
This bug is still extant
I've got this problem working with a Logitech M705 wireless optical mouse and a large display (3840x2160). I've tried fiddling with the mouse Acceleration rate but the mouse still moves by the same amount (i.e. about 1:1) which is murder on the RSI getting the mouse pointer from one side of the screen to the other
Comment 5 Alan Prescott 2020-06-07 19:33:04 UTC
Ok, stet my last. It looks like this was a hardware glitch. I rebooted to Windoze 10 (dual boot) and had the same problems with the mouse so obviously not a software problem. Switched mouse off (again), replaced batteries (again) and then unplugged/replugged wifi dongle and then all Ok. Once the RSI has cooled down a bit I can get back to programming my Python script :-)
Comment 6 Nate Graham 2024-03-25 01:40:34 UTC
Hello! This Bugzilla ticket concerns support for the non-Libinput version of the Mouse page, which is no longer supported in Plasma 6. As such, the ticket will be closed as fixing or implementing what's requested here is now out of scope.

Thanks for your understanding!