Bug 421069

Summary: touchpad settings reset when touchpad is disconnected and re-connected
Product: [Applications] systemsettings Reporter: Mikel Pérez <io>
Component: kcm_touchpadAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version: 5.18.3   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Mikel Pérez 2020-05-05 17:16:35 UTC 
SUMMARY
touchpad settings, like natural scrolling and speed, reset a lot. an obvious one being on disconnect - when reconnected, it behaves as on defaults even as systemsettings reports the settings I want. so I turn device enabled on and off for the apply button to become available and click apply and it's back to my settings

STEPS TO REPRODUCE
1. apply custom (non-default) touchpad settings
2. disconnect touchpad (I'm using a magic trackpad in this case so I just turn it off)
3. reconnect

OBSERVED RESULT
touchpad settings behave as if they were set to their defaults but systemsettings reflects the custom settings

EXPECTED RESULT
touchpad behaving with the custom settings

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 32
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION
this has been happening for a long time since many releases back but it's finally driven me crazy enough for me to file the bug, as it happens a lot, not just on disconnects but that's an easy deterministic one to try
Comment 1 Mikel Pérez 2020-05-05 17:17:35 UTC 
see related #421069 and #419533
Comment 2 Nate Graham 2020-06-22 16:41:57 UTC 
Sounds a bit like Bug 414559.

Does this happen if you manually run `sudo udevadm trigger -s input` in a terminal window?
Comment 3 Mikel Pérez 2020-06-22 16:43:13 UTC 
(In reply to Nate Graham from comment #2)
> Sounds a bit like Bug 414559.
> 
> Does this happen if you manually run `sudo udevadm trigger -s input` in a
> terminal window?

yup, it does
Comment 4 Nate Graham 2020-06-22 16:43:52 UTC 
Thanks!

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