After changing the scrolling distance for my touchpad (elantech on acer aspire v3 771g) it is scrolling too fast and on reentering the settings page I get the message: "Active settings don't match saved settings. You currently see saved settings." After researching I detected, that the slider for vertical and horizontal scrolling reaches from 0.0 to 10.0 mm, but when I set this option with xinput (xinput --set-prop 13 273 50 50) I can set this value from 1 to indef., where 1 is very fast and 50 is normal. Reproducible: Always Steps to Reproduce: 1. Change the scrolling distance in the settings menu and klick apply 2. close settings menu and open it again 3. scroll something 4. check and manipulate settings with xinput Actual Results: after step 2: you get the message: Active settings don't match saved settings. You currently see saved settings. after step 3: the scrolling distance isn't like that, you expected after step 4: you can rise the scrolling distance more than 10 (10mm is the maximum of the slider) (for me 50 is good and >>50 is possible) Expected Results: after step 2: I want to see the settings i setted bevore after step 3: I don't want to scroll as fast as it is after step 4: I expected that the maximum of xinput is equal to the maximum of the slider
In xinput the touchpad is named as "ETPS/2 Elantech Touchpad"
I can confirm this issue here on a MacBook Air 4.2. There seems to be a problem with all the settings which are in millimeter units (so not just horizontal and vertical scrolling, but also e.g. maximal tap move). This completely messes the otherwise very nicely working automatic setup; the problem exists since the major redesign of kcm_touchpad. To get my touchpad working as before I need to manually change them via synclient ( synclient MaxTapMove=535 && synclient VertScrollDelta=243 && synclient HorizScrollDelta=243 ) This problem has also been reported by another user in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/kcm-touchpad/+bug/1308309
Could anybody confirm this problem exists in latest version (1.1)? Because I've already fixed something very similar. *** This bug has been marked as a duplicate of bug 331706 ***
I don't know how to get kcm 1.1...
(In reply to sederic from comment #4) > I don't know how to get kcm 1.1... https://github.com/sanya-m/kcm-touchpad#how-to-install Don't forget to remove corresponding KUbuntu package before installing
Ok, I know have vers. 1.1 installed. The Bug still exists. > Don't forget to remove corresponding KUbuntu package before installing Sorry for asking, but I don't know the apt instance of kcm-touchpad to remove it...