Created attachment 134760 [details] Discover stays on this screen forever, and it only happens with the Addons. SUMMARY Whenever I open Discover and click "Plasma Addons" or "Application addons", it loads indefinitely. Search doesn't work either. STEPS TO REPRODUCE 1. Open Discover 2. Click on "Application addons" or "Plasma addons" OBSERVED RESULT Searching indicator with spinner, category doesn't load. Navigating sub-categories leads to the same result. Browsing normal applications works. EXPECTED RESULT The spinner eventually goes away and a list of addons is presented. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.9.9-arch1-1 OS Type: 64-bit Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 15.5 GiB of RAM Graphics Processor: GeForce GTX 1650/PCIe/SSE2 ADDITIONAL INFORMATION Browsing Plasma widgets from the "Add object" Desktop context menu works just fine.
Can confirm. Still present on Fedora KDE using KDE Plasma 5.20.5 KDE Frameworks 5.78.0 QT 5.15.2 Kernel 5.9.16
Can reproduce if I click on "Application addons" the moment Discover launches. If I first wait until "fetching updates" in the sidebar has changed to "Up to date", and then click on "Application addons", then it finds stuff. This used to work; marking as a regression.
Seems very rare and is easily worked around with no loss of data by restarting the app. Removing from the VHI queue.
In fact this is not rare at all; it is trivially reproduced by launching discover and immediately clicking "Application Addons". Re-launching the app and doing the same thing does *not* work around it. The workaround is to launch the app and then wait 5-20 seconds (depending on your distro) which is not something a user will expect. To them, it will seem that this functionality is totally broken. It may be distro-specific though. I'm on openSUSE Tumbleweed which has a notoriously slow and bad packageKit implementation. I wouldn't be surprised if it works better for for some other distros. However the reporter is on Arch, and another person confirms on Fedora. Perhaps it only works properly on Ubuntu-based distros... Raising to VHI again.
Can I have output of: QT_LOGGING_RULES=org.kde.plasma.libdiscover.debug=true plasma-discover
Edit: QT_LOGGING_RULES=org.kde.plasma.libdiscover.debug=true,org.kde.plasma.libdiscover.backend=true plasma-discover
$ QT_LOGGING_RULES=org.kde.plasma.libdiscover.debug=true,org.kde.plasma.libdiscover.backend=true plasma-discover qt.core.logging: Ignoring malformed logging rule: 'org.kde.plasma.libdiscover.debug=true,org.kde.plasma.libdiscover.backend=true' file:///home/nate/kde/usr/lib64/qml/org/kde/kirigami.2/GlobalDrawer.qml:265: TypeError: Type error file:///home/nate/kde/usr/lib64/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///home/nate/kde/usr/lib64/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///home/nate/kde/usr/lib64/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" adding empty sources model QStandardItemModel(0x309ef40) kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct kf.newstuff.core: The ChecksumPolicy feature is defunct kf.newstuff.core: The SignaturePolicy feature is defunct kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 invalid kns backend! "/home/nate/kde/usr/share/knsrcfiles/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation." org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" file:///home/nate/kde/usr/lib64/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:71:5: QML Binding: Binding loop detected for property "value" Fwupd Error: "Embedded Controller" [ "com.lenovo.ThinkPadN2QHT.firmware" ] cannot be updated Fwupd Error: Cannot Create App From Device Embedded Controller Fwupd Error: "System Firmware" [ "com.lenovo.ThinkPadN2QETXXW.firmware" ] cannot be updated Fwupd Error: Cannot Create App From Device System Firmware
Are you sure this is reproducible in 5.21? 7a4215b7b477de02103af6062b11819fb0c912d2 should have addressed it. And I'm sorry, but adding further debugging information won't work. Testing whether running with only "plasma-discover --backends kns" makes it work better could be useful too.
I'm using git master as of today (as I do every day). Still happening. :( The bug is gone when I do `plasma-discover --backends kns`. If I add the flatpak backend, something different happens when I click on "Applicayion Addons immediately after launching the app: It finishes searching almost immediately, saying "Sorry, nothing found" If I add the packagekit packend, the bug as described here returns.
Interestingly after updating to 5.21 this is working as expected.
This seems to have been fixed in Plasma 5.21!