https://bugs.kde.org/show_bug.cgi?id=513569
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|After boot, Discover can |After boot, Discover can |never open again after |never open again after |being closed |being closed - no SNAP | |backend Status|REPORTED |RESOLVED URL| |https://github.com/getsolus | |/packages/issues/7525 Resolution|--- |DOWNSTREAM Severity|major |normal --- Comment #15 from TraceyC <[email protected]> --- > That is correct. That leads me to believe that fwupd is a dependency of some > aspect of flatpak (or that due to some bug, it's acting like it it when it > shouldn't be), and that in turn leads me to believe the GUI icon for > Discover is set up to internally run with that non-functional flatpak,fwupd > order. The icon for Discover is set up with this invocation line on Solus, it is not set to specify the backends: Program: plasma-discover Command-line arguments: %F I had been hesitant to say this is Solus specific, but after testing other distros, it does appear that way. I'll close this and open an issue with Solus with the details of my troubleshooting there. Testing on the laptop where I can reproduce this: - Starting Discover from the icon produces no journal logs other than the Started line, which is normal - Starting with `plasma-discover --backends fwupd,flatpak` does not bring up the GUI, this shows up in logs after a few moments Jan 06 11:51:45 tracey-solus-aura plasma-discover[144476]: Failed to register name 'org.kde.discover' with DBUS - does this process have permission to use the name, and do no other processes own it already? Jan 06 11:51:45 tracey-solus-aura systemd[1862]: [email protected]: Main process exited, code=exited, status=1/FAILURE Jan 06 11:51:45 tracey-solus-aura systemd[1862]: [email protected]: Failed with result 'exit-code'. - Starting with `plasma-discover --backends fwupd,flatpak` also does not bring up the GUI, same errors - Starting with `plasma-discover --backends flatpak-backend,fwupd-backend` (these are the backends actually listed in --listbackends), no GUI, same errors - Starting with `plasma-discover --backends fwupd-backend,flatpak-backend`, GUI appears This is output on cli $ ~ plasma-discover --backends fwupd-backend,flatpak-backend org.kde.plasma.libdiscover: Plugin "fwupd-backend" doesn't have the right IID "org.kde.discover.6.5.4.AbstractResourcesBackendFactory" expected org.kde.discover.CDDtESsCnLIRnIU0.AbstractResourcesBackendFactory org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true This is in logs Jan 06 12:18:58 tracey-solus-aura plasma-discover[288708]: libostree pull from 'flathub' for appstream2/x86_64 complete Jan 06 12:18:58 tracey-solus-aura plasma-discover[288708]: /var/tmp/flatpak-cache-GI6EI3/repo-JW3Tcz: Pulled appstream2/x86_64 from flathub Jan 06 12:20:47 tracey-solus-aura DiscoverNotifier[2570]: started unattended update QDateTime(2026-01-06 18:20:47.663 UTC Qt::UTC) I tested with other distros, with updates set to be manually applied, after rebooting. There were no problems regardless of backend order - Fedora - (no snap backend on the VM) OK - Neon Testing - OK - OpenSuse Tumbleweed (which also uses appstream) - OK -- You are receiving this mail because: You are watching all bug changes.
