Created attachment 158216 [details] Screenshot STEPS TO REPRODUCE 1. Open Discover 2. Open Settings 3. Click on the three dot menu in the toolbar, choose Configure Updates OBSERVED RESULT System Settings opens, but only shows an empty KCM with the Plasma logo and caption "Plasma System Settings". Journalctl logs ``` QString::arg: 2 argument(s) missing in systemsettings file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "width" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "width" qt.qpa.wayland: Wayland does not support QWindow::requestActivate() ``` EXPECTED RESULT System Settings opens a KCM, where updates can be configured. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230416 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Graphics Platform: Wayland
This means the Updates KCM isn't installed. I suspect you can verify this by running `kcmshell5 --list | grep -i update`. If that doesn't show "kcm_updates" in it, then it's a packaging issue in openSUSE for patching out the Updates KCM.
(In reply to Nate Graham from comment #1) > This means the Updates KCM isn't installed. I suspect you can verify this by > running `kcmshell5 --list | grep -i update`. If that doesn't show > "kcm_updates" in it, then it's a packaging issue in openSUSE for patching > out the Updates KCM. Indeed it doesn't show up. Anyway, I'd expect a hint somewhere at least for the user, so that such upstream bug reports are not necessary. :)
Ok, can you submit a bug report for openSUSE< and we can use this to track a better "KCM not found" UI in System Settings?
(In reply to Nate Graham from comment #3) > Ok, can you submit a bug report for openSUSE< and we can use this to track a > better "KCM not found" UI in System Settings? Done: https://bugzilla.opensuse.org/show_bug.cgi?id=1210706
FTR, it's not patched out, we just have the discover notifier + the KCM in a separate package (discover-notifier) so that it won't be used together with plasma-pk-updates.
(In reply to Fabian Vogt from comment #5) > FTR, it's not patched out, we just have the discover notifier + the KCM in a > separate package (discover-notifier) so that it won't be used together with > plasma-pk-updates. What's not fully clear to me is, why are there two packages and how do they differ? Why can't they be used together and are mutual exclusive? As a user which one do I want to install and why? And why does plasma5-pk-updates not come with the update KCM respectively where do I configure updates when having plasma5-pk-updates installed? :) plasma-notifier > This is a notifier for Discover to inform the user that updates are available and allows the user to install them using Discover. plasma5-pk-updates > Plasma applet for software updates using PackageKit.