Cannot lauch discover

[uni-dos]

Please confirm there isn't an open report for this issue

• [x] I have searched through bug reports

Summary

Discover is not able to launch. Running it from the command line results in no terminal output

Steps to reproduce

1. Launch discover through the terminal or the .desktop

Expected result

See discover

Actual result

Discover is not launched and there are no error messages or output to terminal to debug.

Environment

• [x] Is system up to date?

Repo

Unstable

Desktop Environment

Plasma

System details

System: Host: ryzenbook Kernel: 6.14.4-318.current arch: x86_64 bits: 64 Desktop: KDE Plasma v: 6.3.4 Distro: Solus 4.7 endurance Machine: Type: Laptop System: Framework product: Laptop 13 (AMD Ryzen 7040Series) v: A5 serial: Mobo: Framework model: FRANMDCP05 v: A5 serial: UEFI: INSYDE v: 03.09 date: 04/22/2025 Battery: ID-1: BAT1 charge: 19.5 Wh (39.6%) condition: 49.2/55.0 Wh (89.5%) volts: 15.0 min: 15.4 CPU: Info: 6-core AMD Ryzen 5 7640U w/ Radeon 760M Graphics [MT MCP] speed (MHz): avg: 1116 min/max: 400/4972 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 driver: amdgpu v: kernel Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6 compositor: kwin_wayland driver: gpu: amdgpu resolution: 2256x1504~60Hz API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.5 renderer: AMD Radeon 760M (radeonsi phoenix LLVM 19.1.6 DRM 3.61 6.14.4-318.current) Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor gpu: lact wl: wayland-info x11: xdpyinfo, xprop, xrandr Network: Device-1: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi Drives: Local Storage: total: 953.87 GiB used: 75.81 GiB (7.9%) Info: Memory: total: 28 GiB available: 27.22 GiB used: 3.15 GiB (11.6%) Processes: 353 Uptime: 15m Shell: Bash inxi: 3.3.38

Other comments

Sometimes when executing through the terminal, this is printed org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true adding empty sources model QStandardItemModel(0x564e75dabbc0)

[TraceyC77]

I've run into this on one of my two machines in the nightly build from git-master as well

[SethStormR]

I got the same bug, but on Stable. No error output from the konsole.

[clintre]

I got the same bug, but on Stable. No error output from the konsole.

Have you tried running pkcon update then pkcon refresh

And try launching again

[SethStormR]

Done. But no cigar.

[clintre]

Done. But no cigar.

Couple of more steps we can try... First, lets make sure it is not running in some state... killall plasma-discover

Then try running it with only a single backend to see if it launches For example, we can launch it with just the flatpak backend with...

plasma-discover --backends flatpak-backend

If that does work, then try it with the packagekit backend to see if that is working, which is packagekit-backend

One last thing you can try to see if we get any feedback is plasma-discover --mode update

[SethStormR]

plasma-discover --backends flatpak-backend

This command works and starts Discover. However some output came with it;

org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true
QObject::startTimer: Timers cannot have negative intervals
qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage: Created graphical object was not placed in the graphics scene.

[TraceyC77]

@uni-dos , I just noticed that you missed the issue that had already been opened for this bug. We'll use this one to track progress, since it has more information. Just noting.

[TraceyC77]

plasma-discover --backends flatpak-backend

This command works and starts Discover. However some output came with it;

org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true
QObject::startTimer: Timers cannot have negative intervals
qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage: Created graphical object was not placed in the graphics scene.

That doesn't help, unfortunately. I see that output on a system where Discover launches normally (built from git-master)

On the system (VM on unstable) where Discover does not launch from the App Menu, it can be started with

plasma-discover --backends flatpak-backend

or

plasma-discover --backends packagekit-backend

but not

plasma-discover

even if there are no plasma-discover processes running.

Launching with kns-backend works as well as fwupd-backend.

This does not bring up the Discover UI:

plasma-discover --mode update

[clintre]

I was able to reproduce this on a fresh installation this morning on bare metal as well. I added all the backends in the command line...

plasma-discover --backends packagekit-backend,flatpak-backend,fwupd-backend,kns-backend

and got it to launch. Then I added the command line arguments to the menu entry for Discover, and it ran fine as well.

I was unable to start troubleshooting and digging into the logs at that time due to being at work. But, I have seen mention of this issue with other distros and versions of KDE, but not recently.

So I just loaded up a fresh VM here at home, ran through the same exercise of fresh install and installing Discover and it launches fine. I intended to try to troubleshoot it, but it worked here.

This is a strange issue in that it works fine on my existing install here at home as well as this test VM, but I was able to replicate it on one system, and others can replicate it.

Once I get into my office tomorrow, I will try to dig into the logs and see if I can trace it better.

[clintre]

This is the error I get on my work system... PackageKitBackend: No distro component found for "us.getsol.solus"

Ironically after I launched with the plasma-discover --backends packagekit-backend,flatpak-backend,fwupd-backend,kns-backend

I was able to launch Discover normally after, but it would still log that error.

[TraceyC77]

Ping @sheepman4267 since you had this happen on your machine.

[TraceyC77]

There's now an upstream report

[TraceyC77]

This is an upstream issue caused by a backend failing, probably knewstuff. As such, this isn't something Solus can fix.