Scrolling is too sensitive. The only way to change sensitivity I've found (so I don't know if it's the only one at all (but then maybe there is a problem in design if it's hard to find the proper option)) is to manipulate Scrolling Distance in Scrolling tab, but it could be only worse in my case. Currently I've vertical and horizontal distances at max values (which is 10.0mm). When I set a smaller distance then scrolling becomes even more sensitive. It's hard to scroll web page, because even slight movement scrolls too much of visible area. I think is should be possible to set bigger scrolling Distance. If I'm wrong, then sorry for misunderstanding. I've installed kcm-touchpad 0.9, and then upgraded to 0.99 but the problem is still there. Because I really like the new design I don't want to go back to my previous workarounds for setting touchpad. I've got Lenovo G780 notebook.
Could you post output of "xinput list-props <touchpad-id>" here? To find touchpad id, you could run xinput without arguments. It's really strange if 10mm isn't enough.
Device 'ETPS/2 Elantech Touchpad': Device Enabled (133): 1 Coordinate Transformation Matrix (135): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (262): 1 Device Accel Constant Deceleration (263): 2.500000 Device Accel Adaptive Deceleration (264): 1.000000 Device Accel Velocity Scaling (265): 12.500000 Synaptics Edges (287): 117, 2823, 68, 1192 Synaptics Finger (288): 1, 1, 0 Synaptics Tap Time (289): 180 Synaptics Tap Move (290): 20 Synaptics Tap Durations (291): 180, 180, 100 Synaptics ClickPad (292): 0 Synaptics Middle Button Timeout (293): 75 Synaptics Two-Finger Pressure (294): 282 Synaptics Two-Finger Width (295): 7 Synaptics Scrolling Distance (296): 10, 10 Synaptics Edge Scrolling (297): 0, 0, 0 Synaptics Two-Finger Scrolling (298): 1, 1 Synaptics Move Speed (299): 1.000000, 10.930648, 0.062539, 0.000000 Synaptics Off (300): 1 Synaptics Locked Drags (301): 0 Synaptics Locked Drags Timeout (302): 5000 Synaptics Tap Action (303): 0, 0, 0, 0, 1, 2, 3 Synaptics Click Action (304): 1, 1, 1 Synaptics Circular Scrolling (305): 0 Synaptics Circular Scrolling Distance (306): 0.100007 Synaptics Circular Scrolling Trigger (307): 0 Synaptics Palm Detection (308): 0 Synaptics Palm Dimensions (309): 10, 200 Synaptics Coasting Speed (310): 20.000000, 50.000000 Synaptics Pressure Motion (311): 30, 160 Synaptics Pressure Motion Factor (312): 1.000000, 1.000000 Synaptics Grab Event Device (313): 1 Synaptics Gestures (314): 0 Synaptics Capabilities (315): 1, 0, 1, 1, 1, 1, 1 Synaptics Pad Resolution (316): 1, 1 Synaptics Area (317): 0, 0, 0, 0 Synaptics Noise Cancellation (318): 15, 15 Device Product ID (251): 2, 14 Device Node (252): "/dev/input/event16"
> Synaptics Pad Resolution (316): 1, 1 Here is the problem. The driver reports wrong resolution. As a workaround, I've increased max. scrolling distance, patch is already in master branch. Maybe I'll also add lower bound for resolution, so "unknown" will be, for example, 10,10 instead of 1,1.
Thanks! Compiled from git, tested and it works with values 20mm, 20mm. Now, should I report problem with driver (in Linux I guess), so this workaround won't be necessary in the future?
(In reply to comment #4) > Thanks! Compiled from git, tested and it works with values 20mm, 20mm. > > Now, should I report problem with driver (in Linux I guess), so this > workaround won't be necessary in the future? I think it's a known problem. It looks like the driver properly sets "Synaptics Edges" property. I think approximate resolution could be computed from it.
Git commit 008ead68ea69e73cb548d70f901d94a315f52d37 by Alexander Mezin. Committed on 07/03/2014 at 16:11. Pushed by alexandermezin into branch 'master'. X11 backend: when resolution is unknown, approximate using "edges" Though I am not able to test if it works correctly M +12 -2 src/backends/x11/xlibbackend.cpp http://commits.kde.org/kcm-touchpad/008ead68ea69e73cb548d70f901d94a315f52d37
Could you confirm if the problem is solved with latest git master, please? Now values near 2-3 mm should be sufficient.
I don't think there is any change. I still have to stick with 20mm.
1. Make sure you have latest version from git. If you're still able to set 20mm, then you're not using it, as I've changed max distance back to 10mm. 2. Enable debug output for kcmshell4 (using kdebugdialog), and disable for everything else. Run "kcmshell4 kcm_touchpad" in terminal, and attach/post its output here.
1. Checked. 2. I have no kcmshell4 in kdebugdialog, but I still can launch command 'kcmshell4 kcm_touchpad'.
(In reply to comment #10) > 2. I have no kcmshell4 in kdebugdialog, but I still can launch command > 'kcmshell4 kcm_touchpad'. Oh, sorry, my mistake. There aren't any "kcmshell4" in kdebugdialog, but there are "kcmshell" instead.
Git commit 9007344a1a11315eb4b08a77f6935fb4cddb4051 by Alexander Mezin. Committed on 11/03/2014 at 20:35. Pushed by alexandermezin into branch 'master'. X11 backend: another resolution detection fix Previous fix contained a bug - scaling wasn't enabled for properties when fallback algorithm was used. M +19 -20 src/backends/x11/xlibbackend.cpp http://commits.kde.org/kcm-touchpad/9007344a1a11315eb4b08a77f6935fb4cddb4051
Could you please check again if it works correctly now?
Sorry, have no time. No I have :) When I start kdebugdialog there is no entry with *shell*, especially 'kcmshell' / 'kcmshell4'. No I'll check new version.
(In reply to comment #14) > When I start kdebugdialog there is no entry with *shell*, especially > 'kcmshell' / 'kcmshell4'. I need debug output only if you still have to set maximum possible scrolling distance.
Now works as it should. 2mm / 2mm is good. Great job with new kcm module. Thanks! :)
*** Bug 333491 has been marked as a duplicate of this bug. ***
Exact same issue on a macbook air 11" with kubuntu 14.04 (kcm 0.99) xinput list-props 11 Device 'bcm5974': Device Enabled (135): 1 Coordinate Transformation Matrix (137): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (265): 1 Device Accel Constant Deceleration (266): 2.500000 Device Accel Adaptive Deceleration (267): 1.000000 Device Accel Velocity Scaling (268): 12.500000 Synaptics Edges (269): -3791, 4311, 423, 6027 Synaptics Finger (270): 70, 75, 0 Synaptics Tap Time (271): 180 Synaptics Tap Move (272): 20 Synaptics Tap Durations (273): 180, 180, 100 Synaptics ClickPad (274): 1 Synaptics Middle Button Timeout (275): 0 Synaptics Two-Finger Pressure (276): 283 Synaptics Two-Finger Width (277): 7 Synaptics Scrolling Distance (278): 10, 10 Synaptics Edge Scrolling (279): 1, 0, 0 Synaptics Two-Finger Scrolling (280): 1, 0 Synaptics Move Speed (281): 1.000000, 1.750000, 0.016855, 0.000000 Synaptics Off (282): 2 Synaptics Locked Drags (283): 0 Synaptics Locked Drags Timeout (284): 5000 Synaptics Tap Action (285): 2, 3, 0, 0, 1, 3, 0 Synaptics Click Action (286): 1, 3, 0 Synaptics Circular Scrolling (287): 0 Synaptics Circular Scrolling Distance (288): 0.100007 Synaptics Circular Scrolling Trigger (289): 0 Synaptics Circular Pad (290): 0 Synaptics Palm Detection (291): 0 Synaptics Palm Dimensions (292): 10, 200 Synaptics Coasting Speed (293): 248.880005, 44.619999 Synaptics Pressure Motion (294): 30, 160 Synaptics Pressure Motion Factor (295): 1.000000, 1.000000 Synaptics Resolution Detect (296): 1 Synaptics Grab Event Device (297): 1 Synaptics Gestures (298): 1 Synaptics Capabilities (299): 1, 0, 0, 1, 1, 1, 1 Synaptics Pad Resolution (300): 1, 1 Synaptics Area (301): 0, 0, 0, 0 Synaptics Soft Button Areas (302): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (303): 39, 27 Device Product ID (255): 1452, 656 Device Node (256): "/dev/input/event8" It is quite anoying because even with 10mm the scrolling is *way* too fast. What should I test/compile??
Never mind : I have complied the current git version and it works like a charm. The kubuntu package should be updated (I'm going to write a separate bug report).
*** Bug 337190 has been marked as a duplicate of this bug. ***
*** Bug 339914 has been marked as a duplicate of this bug. ***
Today I updated to the latest plasma on my openSUSE Leap and this bug appeared again on my Lenovo Thinkpad T410. The vertical scroll speed is way to senstive again, even when set to 10mm.
I can confirm I also experience this regression with recent update (Plasma 5.5.95). Setting it to 80 via "synclient VertScrollDelta=80 HorizScrollDelta=80" gives desired result, but it is impossible to set these values via UI.
I can also confirm the bug on openSUSE tumbleweed (plasma 5.5.5). Igor's command fixes it from the terminal.
Indeed, Igors command is a workaround. Maybe we should open a new bug, since this is a regression??
Recent update (Plasma 5.6.1; maybe also 5.6.0, not sure) fixed this problem for me.
I can confirm. Upgraded to 5.7 beta today and the problem is gone.
Since there was no update since June, closing this. Feel free to reopen if it is still an issue.