| Summary: | Discover fails to completely close on quit, remains open in the background, and doesn't start via a GUI method | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | kenwgreen |
| Component: | KNewStuff Backend | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | ASSIGNED --- | ||
| Severity: | major | CC: | 4wy78uwh, aleixpol, kdedev, leinir, nate, sitter |
| Priority: | HI | ||
| Version First Reported In: | 6.3.4 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| URL: | https://discuss.kde.org/t/plasma-discover-not-launching/12503/30 | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=510390 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
kenwgreen
2025-07-19 06:07:44 UTC
I've been seeing this on git-master on one laptop, but not in git-master or 6.4.3 on another laptop, both with Solus. Other Solus users have run into it https://github.com/getsolus/packages/issues/5623 We noticed that if Discover doesn't launch from the menu, it has a process in the process tree but no gui If launched from command line with no arguments, there are no errors The GUI can be launched if one or more backends are passed in on command line e.g. plasma-discover --backends packagekit-backend --backends flatpak-backend Probably knewstuff acting up again. Will need to find a way to reproduce and track down why it actually gets stuck. :( I have been playing with Discover and the backend addons. I have found that uninstalling Discover-Snap backend addon that the Discover app launches every time without fail. I only have to remove the Snap addon leaving the Flatpak and PackageKit addons installed,so it would appear there is some issue with Discover and the Snap backend *** Bug 510390 has been marked as a duplicate of this bug. *** There's some debugging info in Bug 510390. Would anyone be able to try this change? It would help us by printing if there's any outstanding Transactions that are never resolving themselves. https://invent.kde.org/plasma/discover/-/merge_requests/1194 I see harald suggested that it might be KNS but it seems snap might be related too. (In reply to Aleix Pol from comment #7) > Would anyone be able to try this change? It would help us by printing if > there's any outstanding Transactions that are never resolving themselves. Would be difficult to confirm without a consistent reproduction method. > I see harald suggested that it might be KNS but it seems snap might be > related too. I've definitely not ever had Snap installed, yet have experienced this, so it's not the *sole* cause, if so. Fair enough, maybe it's both. Some people have claimed to be able to reproduce the issue reliably following the links. (In reply to Aleix Pol from comment #9) > Fair enough, maybe it's both. > > Some people have claimed to be able to reproduce the issue reliably > following the links. Absolutely I can reproduce and indeed just to confirm I have as at the date and time of this reply;- 1. Open Discover 2. Re-installed Snap back-end via Discover. 3. Closed Discover 4. Tried to re-open without success. 5. $ pkill discover 6. $ plasma-discover --backends packagekit-backend 7. Uninstalled Snap back-end 8. Open Discover, no issue 9. Close and re-open Discover no issue Conclusion Discover Snap Backend is the issue. A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/1196 Any of the people who can reproduce the issue, we'd very much appreciate some testing. Alternatively, could you see if the process ends after about 80s of closing it? Tried after re-installing Snap-Backend, waited 80 seconds I assume, still the Discover app failed to load. Un-installed the snap-backend and Discover launched no issue. |