| Summary: | With KNewStuff backend loaded, Discover fails to fully exit on quit, causing it to not launch again | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Alpha-Craft <knolld00> |
| Component: | KNewStuff Backend | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | aleixpol, john.kizer, leinir, nate, sitter |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Alpha-Craft
2025-04-15 10:24:39 UTC
Is this 100% reproducible, including when you run `plasma-discover` in a terminal window and then quit it by clicking its close button? If so, let's go backend by backend and see which one is hanging on quit. Run `plasma-discover --listbackends`. It will spit out something like this: Available backends: * fwupd-backend * flatpak-backend * packagekit-backend * kns-backend Then please open Discover with one backend at a time with `plasma-discover --backends [the backend name]` e.g `plasma-discover kns-backend`. Then quit by clicking on the close button. Ideally one of them will hang on close and we'll be able to know which one it is! (In reply to Nate Graham from comment #1) > Is this 100% reproducible, including when you run `plasma-discover` in a > terminal window and then quit it by clicking its close button? > > If so, let's go backend by backend and see which one is hanging on quit. Run > `plasma-discover --listbackends`. It will spit out something like this: > > Available backends: > * fwupd-backend > * flatpak-backend > * packagekit-backend > * kns-backend > > Then please open Discover with one backend at a time with `plasma-discover > --backends [the backend name]` e.g `plasma-discover kns-backend`. Then quit > by clicking on the close button. > > Ideally one of them will hang on close and we'll be able to know which one > it is! I have done the testing and for one, it also happens when I am launching it via the terminal with `plasma-discover`. I also tested the individual backends, and the single one backend that appears to hang is the *kns-backend*. Everything else worked just fine. Thanks. I had a feeling it was going to be KNS. Disappointing to hear that it's still happening in Plasma 6.3.4 with Frameworks 6.13; I had thought we squashed this bug. @sitter another notch in favor of deleting KNS functionality entirely... Interestingly, with the system below, I can't reproduce this - just to check, are you still able to reproduce after the latest updates, including the Qt 6.9 ones? Thanks! Operating System: Fedora Linux 42 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 Kernel Version: 6.14.2-300.fc42.x86_64 (64-bit) 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. This is still hapenning. I need to check whether there are updates to QT and I am planning to upgrade from Fedora KDE 41 to version 42 very soon. OK, let us know! (In reply to Nate Graham from comment #8) > OK, let us know! I upgraded my installation today and have QT 6.9. The issue still persists. This bug has been fixed with Plasma 6.4. Closing. |