Created attachment 187788 [details] Showing 5 simultaneous Discover processes (none of which produce a useable window or closeable instance on the taskbar). SUMMARY After booting up Solus, if I ever need to use Discover to manage my applications, and I think I'll ever need to use it again for the remainder of my PC's time running, I cannot close Discover again. If I do, I will not be able to open it back up before rebooting. STEPS TO REPRODUCE 1. Start up PC, sign in (my OS is Solus) 2. Open Discover. Use it or don't use it -- doesn't matter. 3. Close Discover. 4. Try to open Discover again: from the taskbar, from the start menu, whatever manner. It will fail to open. OBSERVED RESULT Not only does Discover fail to reopen, but in the System Monitor, we can see that it opens up a new Discover process every single time we try to open it, and they remain forever, stacking up. EXPECTED RESULT If the application worked properly, after closing Discover, it would be easy, trivial to reopen it with a click on any of the places to find it (taskbar, start menu...). Furthermore, it would not keep spinning up new processes that get permanently stuck. SOFTWARE/OS VERSIONS Solus Linux: 4.8 Opportunity Budgie UI: 10.9.4 ADDITIONAL INFORMATION Kernel: Linux 6.17.8-324.current An existing bug report, 375804, has been made for this issue. However, it was automatically closed because of the unresponsive bug report author. I will do what I can to help this issue get fixed, though I am not very knowledgeable. The last message to the author in that thread was about running Discover through GDB. I do not know how to do that, so please let me know (if that is even the right thing to do here). The existing bug report was filed for Discover version 5.8.5, making this a fairly old issue. In the attached image, you can see the 5 simultaneous Discover processes (none of which produce a useable window or closeable instance on the taskbar).
Is this issue reproducible for you? It happens at every login? If so, can you run `plasma-discover --backends packagekit,flatpak,fwupd` and then quit the app and see if the issue still happens? I'm suspecting it *will not* happen. If that's correct, then do it again with `plasma-discover --backends packagekit,flatpak,fwupd,kns` and quit the app and see if it still happens. I'm suspecting that it *will* happen.
(In reply to Nate Graham from comment #1) > Is this issue reproducible for you? It happens at every login? > > If so, can you run `plasma-discover --backends packagekit,flatpak,fwupd` and > then quit the app and see if the issue still happens? I'm suspecting it > *will not* happen. > > If that's correct, then do it again with `plasma-discover --backends > packagekit,flatpak,fwupd,kns` and quit the app and see if it still happens. > I'm suspecting that it *will* happen. Yes, it is reproducible, every single login. I followed your instructions and the app still failed. I'm adding a new attachment for these commands. In the first attempt, which was run while Discover was open, something seems to have happened, but despite your theory, it did not prevent the issue from happening. The future attempts were made in the same boot and you can see they did not resolve in any manner at all, and had to be forcefully terminated.
Created attachment 187806 [details] Bugged results of running recommended commands.
Any new thoughts? I just want to make sure my update didn't slip through the cracks.
I got the email about it; you'll just need to be a bit patient, especially around the end of the year when lots of folks are on vacation. I do understand how frustrating this must be, but the good news is that since you can reproduce it 100% of the time, that will make the debugging simpler.
The holidays are quite understandable! This was all I needed to hear, it's not urgent (I don't need to install software every single day).