Bug 461332 - 'Acceleration profile' settings are disappearing on some ocasions.
Summary: 'Acceleration profile' settings are disappearing on some ocasions.
Status: RESOLVED DUPLICATE of bug 448953
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 5.24.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-02 20:36 UTC by hotmusicfan
Modified: 2022-11-04 18:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot-KCM_Touchpad-Available (125.19 KB, image/png)
2022-11-02 20:36 UTC, hotmusicfan 		Details
Screenshot-KCM_Touchpad-Unavailable (111.58 KB, image/png)
2022-11-02 20:37 UTC, hotmusicfan 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description hotmusicfan 2022-11-02 20:36:58 UTC 
Created attachment 153411 [details]
Screenshot-KCM_Touchpad-Available

SUMMARY
Hello all! 🙂
I recently performed a system upgrade to openSUSE Leap 15.4 which ships KDE Plasma 5.24.4 and KDE Frameworks 5.90.0. 
I needed to tweak the touchpad because after the upgrade it didn't worked as good as previously. For that goal I needed to experiment with the settings and I noticed that some of them (the marked ones on the screenshots below) are sometimes disappearing. They re-appear on some ocasions , e.g. if I press 'Reset' or re-install Synaptics/libinput driver.
SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.4
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.14.21-150400.24.28-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-2760QM CPU @ 2.40GHz
Memory: 7,7 GiB of RAM
Graphics Processor: Quadro 1000M/PCIe/SSE2
Comment 1 hotmusicfan 2022-11-02 20:37:47 UTC 
Created attachment 153412 [details]
Screenshot-KCM_Touchpad-Unavailable
Comment 2 Nate Graham 2022-11-04 18:37:31 UTC 

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