I am using KDE Fedora 41 (KDE plasma version 6.2.4) and the discover app store started getting stuck on fetching updates and never completes actually fetching updates. Is there any proper fix for this?
Screenshot:
what happens when you run plasma-discover command in a console window?
It opened Discover. But the fetching updates keeps happening:
$ plasma-discover
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true
adding empty sources model QStandardItemModel(0x5564de822380)
qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage: Created graphical object was not placed in the graphics scene.
qrc:/qt/qml/org/kde/discover/qml/UpdatesPage.qml:11:1: QML UpdatesPage: Created graphical object was not placed in the graphics scene.
qrc:/qt/qml/org/kde/discover/qml/UpdatesPage.qml:40:5: QML OverlaySheet: Binding loop detected for property "y":
file:///usr/lib64/qt6/qml/org/kde/kirigami/templates/OverlaySheet.qml:110:5
Also one thing I noted is that it completes at some point but it takes a very long time. and I mean a very very long time.
maybe change the server it points to using the setting in the driver manager, there is likely more than one mirror for your locale.
1 Like
If you don’t have the packagekit backend, all discover is really doing is updating flatpaks and doing fwupd updates (firmware).
So ignoring the firmware part. You could do the same thing as discover would do with the command line command:
flatpak update
I do that all the time, because I’ll run discover, see the flatpak update(s) are there, then I’ll exit out of discover to run
flatpak update
on the command line because the command feedback is way more detailed than what the Discover GUI shows
2 Likes