In my enviroment, the available backends are listed as follows:
plasma-discover --listbackends
libEGL warning: egl: failed to create dri2 screen
Available backends:
libs QList("/usr/lib/x86_64-linux-gnu/qt6/plugins", "/usr/bin")
* packagekit-backend
* snap-backend
* kns-backend
* flatpak-backend
* fwupd-backend
When loading the backends in this sequence (with packagekit loaded first):
plasma-discover will not respond.
$ plasma-discover --backends packagekit,snap,kns,flatpak,fwupd
libEGL warning: egl: failed to create dri2 screen
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
adding empty sources model QStandardItemModel(0x5edef99063e0)
However, if packagekit is moved to the last position in the sequence, plasma-discover starts normally.
$ plasma-discover --backends snap,kns,flatpak,fwupd,packagekit
libEGL warning: egl: failed to create dri2 screen
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
adding empty sources model QStandardItemModel(0x5c43fe86ec10)
looking up wrong category or too early "Games"
looking up wrong category or too early "Development"
qrc:/qt/qml/org/kde/kirigami/private/PrivateActionToolButton.qml:71:5: QML Binding: Binding loop detected for property "value":
qrc:/qt/qml/org/kde/kirigami/private/PrivateActionToolButton.qml:74:9
Sadly, I didn’t find any configuration file to change the backend loading sequence. The only workaround is to add a startup argument.
