SUMMARY Touchpad settings are not loaded upon login, until you manually toggle any option in Touchpad KCM page and hit Apply. If you do that, any modifications will be reverted (instead of being applied), but you'll get all your previously set options active once again. I recorded this video on a brick-phone (thus pardon for the quality) so I could show my hands' movement in sync with what's going on the screen. https://youtu.be/BPGYmdSnVDc STEPS TO REPRODUCE 1. Start KDE/Plasma X11 session. 2. Open System Settings -> Input -> Touchpad. 3. Toggle any checkbox. 4. Hit Apply. OBSERVED RESULT Touchpad is back to its "usual settings" instead of factory default, KCM is unusable in a sense that it has no effect other than somehow triggering system to load those previous "usual settings". EXPECTED RESULT Touchpad should work normally. Settings should be applied to it as soon as user logs in. Touchpad KCM should correctly save its preferences. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.15.11-arch2-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970M/PCIe/SSE2 ADDITIONAL INFORMATION Built from git master, fairly recent, 26th of December
Reminds me a bit of Bug 397971. Cannot reproduce on Wayland on Fedora 35.
> Reminds me a bit of Bug 397971. Symptoms are similar. At some point, I recall I was looking mouse preferences too; hence I tried to connect a mouse and mess with its KCM in the video. But somehow mouse works OK for me. I don't know which logs to collect, or which services to debug. Any ideas? > Cannot reproduce on Wayland on Fedora 35. I'm pretty sure it's some platform code which is as close to X and input handling as it might get.
So, thanks to our experienced guys we fixed the keyboard KCM and xkb integration. Now, how about unbreaking the touchpad. Confirming the bug for myself, because the video I posted should be proof enough. I'd say this is legible for the 15-minute bug list. After participating in fixing keyboard layout I have a rough idea where to start debugging.
Sounds related to https://bugs.kde.org/show_bug.cgi?id=449230
(In reply to Nicolas Fella from comment #4) > Sounds related to https://bugs.kde.org/show_bug.cgi?id=449230 On second thought I don't think it's related.
fwiw I cannot reproduce this on X11. Can you reproduce this on a clean installation, i.e. no self-built Plasma on top of Distro Plasma? This sounds like the kcminit part of the KCM isn't loading to restore the settings, and I remember that there was some trouble with that in self-built sessions due to leftover files from an internal migration
Could be related to Bug 435113. Are you still able to reproduce it, though? We haven't gotten any new reports.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Touchpad is OK for me lately, but mouse it still being reset upon login.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!