Bug 407613 - Touchpad settings are missing or greyed out
Summary: Touchpad settings are missing or greyed out
Status: RESOLVED DUPLICATE of bug 398228
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 5.17.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-16 18:51 UTC by Matej Mrenica
Modified: 2020-01-22 21:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot1 (99.77 KB, image/png)
2019-05-16 19:00 UTC, Matej Mrenica
Details
Screenshot2 (124.08 KB, image/png)
2019-05-16 19:01 UTC, Matej Mrenica
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matej Mrenica 2019-05-16 18:51:14 UTC
STEPS TO REPRODUCE
1. Open Systemsettings -> Input Devices -> Touchpad (touchpad KCM is missing see screenshot1)
2. Now open Mouse and then Touchpad again (now touchpad KCM is there but greyed out see screenshot2)

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.15.90
KDE Frameworks Version: 5.58
Qt Version: 5.13.0 beta3

ADDITIONAL INFORMATION
On wayland, possible duplicate of https://bugs.kde.org/show_bug.cgi?id=395351
Comment 1 Matej Mrenica 2019-05-16 19:00:42 UTC
Created attachment 120117 [details]
Screenshot1
Comment 2 Matej Mrenica 2019-05-16 19:01:10 UTC
Created attachment 120118 [details]
Screenshot2
Comment 3 atulbi 2019-05-17 05:16:39 UTC
I can also reproduce a similar bug.

Starting with kcmshell5, Both mouse and touchpad KCM can be opened without any problems on kcmshell5.

On X11 when both mouse(wireless in my case) and touchpad are connected.
On system settings, If I first open touchpad KCM, then everything is fine.
but if I open mouse KCM first and then touchpad KCM, I'm getting similar as Screenshot2.

On wayland, whatever opens first works. The other one is all greyed.

IMHO, it is because System settings is processing the same qml file which is opened first.
Comment 4 Patrick Silva 2019-05-17 11:18:43 UTC
bug 398228 is related/duplicate
Comment 5 atulbi 2019-05-18 11:07:33 UTC

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