Discover crashes on start, no console messages

Help
,
1

After a few system updates - no idea what exactly - Discover is crashing now. Yesterday I upgraded to the new 24.04 LTS for Neon, and Discover was fine after that. Launching from a terminal causes it to launch in a separate process - it just returns to the command prompt without any messages.
How do I check for what’s causing it?

Update - it launches with a warning about running as root if I start it from a sudo su shell.
Console shows

libs QList("/usr/lib/x86_64-linux-gnu/qt6/plugins", "/usr/bin")
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true
adding empty sources model QStandardItemModel(0x64138d730210)
qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth"
qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "calculatedImplicitHeight"
qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:401:33: QML Binding: Binding loop detected for property "value"
qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage: Created graphical object was not placed in the graphics scene.
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth"
qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "calculatedImplicitHeight"
2

Similar error here

Discover does not show any GUI. Process is running, but I can not see anything.

If I start it from konsole

plasma-discover
libs QList("/usr/lib/x86_64-linux-gnu/qt6/plugins", "/usr/bin")
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true
adding empty sources model QStandardItemModel(0x5ea1f1e1c020)
3

It’s working now - there was a large update of various packages yesterday that probably fixed it.

4

I updated today and it is still not working.

5

The problem was snap backend - “plasma-discover-backend-snap”.

After uninstalling this, discover started.