Problem launching Discover since the third time during the same session

penny-farthing

I noticed this, last week. When launching Discover (on Budgie desktop), for example, to process an update or search for an application, you naturally close the application after each use.

Today, on the third attempt (I wanted to perform another search), the Discover window didn't appear. The icon in the taskbar blinked at least twelve times and then stopped blinking.

When I launch the application on the terminal, here's the result:

administrateur@solus-pc ~ $ plasma-discover --verbose
Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.
discover: Unknown option 'verbose'.
QThreadStorage: entry 2 destroyed before end of thread 0x5585a5f5c250
QThreadStorage: entry 1 destroyed before end of thread 0x5585a5f5c250
administrateur@solus-pc ~ $

What can be done to fix this issue?
Thank you in advance for your help.

Note that this can happen since the 2nd launch of Discover in the same session.
Also note that, in that case, you can only access Discover normally by restarting the computer (closing the session is not enough).

MikeK61

Did you try pkill Discover ?

Also you can try to start with
plasma-discover --backends packagekit,snap,fwupd,flatpak

Works for me.

penny-farthing

MikeK61

Yes, it works with your terminal commands 👍, that's good to know for troubleshooting purposes, thank you:

administrateur@solus-pc ~ $ pkill plasma-discover
administrateur@solus-pc ~ $ plasma-discover --backends packagekit,snap,fwupd,flatpak
Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
adding empty sources model QStandardItemModel(0x55d0c5507a40)
org.kde.plasma.libdiscover: Plugin "snap-backend" doesn't have the right IID "" expected org.kde.discover.6.5.3.AbstractResourcesBackendFactory
qrc:/qt/qml/org/kde/discover/qml/Feedback.qml:4:1: module "org.kde.userfeedback" is not installed
PackageKitBackend: No distro component found for "us.getsol.solus"
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
AppStreamIntegration: No distro component found for "us.getsol.solus"
qrc:/qt/qml/org/kde/discover/qml/UpdatesPage.qml:40:5: QML OverlaySheet: Binding loop detected for property "y":
qrc:/qt/qml/org/kde/kirigami/templates/OverlaySheet.qml:117:5
administrateur@solus-pc ~ $

TraceyC

MikeK61 Did you try pkill Discover ?

Also you can try to start with
plasma-discover --backends packagekit,snap,fwupd,flatpak

This is mentioned in the known Issues. Always remember to check there when encountering problems. This is an upstream issue KDE is going to have to fix.

Glad to hear the workaround is working for you both in the meantime.

Patrice

Use Solseek ..... 😆
I am out ....[]

penny-farthing

Patrice

That's true, I admit I was kind of expecting it... 😊

That said, Solseek is brand new, and we also need to think about the users who will continue to use Discover (and Gnome Software) for whom this could become problematic.

Furthermore, I'd like to remind you of Harvey's comments in a previous post where he explained that Discover or Gnome Software will remain the default operating system and recommendation:
https://discuss.getsol.us/d/12107-solus-update-post-for-week-45-2025/99

penny-farthing

TraceyC

Thanks for the advice, I'll try to remember it in the future.

PS. Sorry for not replying sooner; I was without Solus for almost two days because of the Plymouth package which prevented my computer from restarting, but the problem is now fixed.