Created attachment 115195 [details] "Active settings don't match saved settings" SUMMARY STEPS TO REPRODUCE 1. Enable "Reverse scrolling" in Settings > Input Devices > Touchpad > Scrolling 2. After a while, this setting will be reversed 3. System Settings will show "Active settings don't match saved settings" (see screenshot) EXPECTED RESULT "Reverse scrolling" setting will be kept. ACTUAL RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION
Some reddit users are experiencing this issue too: https://www.reddit.com/r/kde/comments/8u2g3q/touchpad_scroll_settings_getting_reset/
I have found a way to reproduce it 100% of the time: disabling and enabling touchpad using the dedicated keyboard key.
I can confirm the bug with Plasma 5.13.5-1 on Fedora 29 (see https://bugzilla.redhat.com/show_bug.cgi?id=1643460 for the downstream bugreport). It also happens when plugging/unplugging a USB mouse. $ kcm-touchpad-list-devices | grep TOUCHPAD Name: Synaptics TM2911-001 Type: TOUCHPAD Use: Extension Pointer
Same for me. When I open touchpad settings on Kubuntu 18.10, after restart I see an information that data stored are different than shown in a dialog box. When I reset and save settings it is being fixed.
Same happens here every time after unlocking the desktop. Name: DLL0665:01 06CB:76AD Touchpad Type: TOUCHPAD Use: Extension Pointer 5.13.5 on Fedora 29 From this: [761738.410] (II) event7 - DLL0665:01 06CB:76AD Touchpad: device removed [761739.221] (II) event7 - DLL0665:01 06CB:76AD Touchpad: is tagged by udev as: Touchpad [761739.221] (II) event7 - DLL0665:01 06CB:76AD Touchpad: device is a touchpad seems like something gets lost on locking and after coming back settings are not applied.
Well, for me, it is a mouse/touchpad settings conflict. Setting "Inverse scrolling" to true in kcm's mouse setting "fixes" it for me.
Thanks Michael, it solves a problem also in my case.
Seems like this bug has been fixed in Plasma 5.14.0, see bug#395722. :) *** This bug has been marked as a duplicate of bug 395722 ***