Bug 435205

Summary: No ability to set scroll wheel parameters in system settings
Product: [Applications] systemsettings Reporter: Jorn_Haga <bjornlasanche>
Component: kcm_mouseAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: major CC: bjornlasanche
Priority: NOR    
Version First Reported In: 5.18.6   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=435245
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: screenshot showing mouse settings has no additional tabs as per the Mouse Help doc

Description Jorn_Haga 2021-04-01 02:32:29 UTC
Created attachment 137216 [details]
screenshot showing mouse settings has no additional tabs as per the Mouse Help doc

When using my mouse for editing documents as well as Audio production, the use of the scroll wheel is imperative as is the means to adjust its settings. The current ability to adjust the settings of the scroll wheel, as well as other settings of the mouse's functions are simply not there.  The help documentation says they are, but enclosed is a screenshot showing that there are no separate tabs as per the help documentation for mouse settings.  The only scroll wheel setting is to invert the scroll which is unsatisfactory.  When scroll wheel is used now the movement jumps on average 3/4-2-1/2 pages depending on the zoom level.  The zoom level is tied to the setting of the scroll wheel movement so why is it removed?  


STEPS TO REPRODUCE
1. Application Launcher/System Settings/Hardware/Input Devices/Mouse
2. Type System Settings in upper box in Application Launcher then Hardware/Input Devices/Mouse
3. Open Yast Repeat above to get to same place.

OBSERVED RESULT
The following settings are missing:
Pointer threshold
Double click interval
Drag start time and Drag start distance
Mouse wheel scrolls by    (This is HUGE omission as it affects many other input options, zoom for one.  Hitting Ctrl+scroll wheel I get options of maybe one two two huge visually words on the screen, or so small I cannot determine what the words are unless having a magnifying glass in hand and this is on a 4k 42" flat screen.)

All potential settings under Keyboard Navigation in the Mouse Help doc.

Clicking on the touchpad tab does bring up a window which allows one to test scroll function, but all ability to change settings are non-functional and greyed out.

Several settings dealing with the mouse are in the Windows Behavior section of the System Settings under General Behavior and Windows Effects, but none pertain to the issue at hand.



EXPECTED RESULT
The ability to not have to hunt for settings that are necessary.  If a feature is removed, remove it out of the documentation as well BEFORE implementing the change.  While I am sure I can dig into the library files and locate the settings and change them myself to my liking, why should I have to?  Not all Linux users are coders, nor should they be expected to be for simple I/O concerns.  This is not due to the installment on any application outside the main OS.  These are internal settings that are just gone. 


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 15.2 OpenSUSE Leap
(available in About System)
KDE Plasma Version: 5.18.6
KDE Frameworks Version: 5.71.0
Qt Version: 5.12.7

ADDITIONAL INFORMATION


These functions need to be able to be set to fine detail for audio work. I am talking pixel size movement settings. I make money editing audio for a portion of my income and the way the scroll settings are now is a deal breaker.  Is there a way to manually set the GPM in the meantime?
Comment 1 2wxsy58236r3 2021-04-02 02:06:25 UTC
Please refer to Bug 430742 Comment 1:

> You must be using the Libinput driver on X11. This feature cannot be
> implemented for this use case due to lack of support in Libinput itself

> On Wayland the situation is different, and we have already implemented a
> scroll speed feature.

You can switch to evdev driver on X11 as a workaround. KDE will show you a different set of settings if evdev is used.

*** This bug has been marked as a duplicate of bug 430742 ***