SUMMARY When searching for an app, Discover is stuck at "Still looking..." with the spinning gear. STEPS TO REPRODUCE 1. Open Discover; 2. Search for an app (i.e. "KleverNotes") using the text field up on the left; 3. Observe Discover behaviour. OBSERVED RESULT Discover search is stuck at "Still looking..." with the spinning gear for an apparently indefinite amount of time. EXPECTED RESULT Discover search returns something, or at least tells you what it is currently doing / waiting on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 Linux/KDE: Fedora 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1
The issue of the busy indicator being misplaced is Bug 488267. As for the functional issue, does it *ever* find anything? Like, after, say, 30 minutes? Or is it still stuck at that point? If so, does the issue reproduce in a new clean user account on the same machine? If so, does the issue reproduce in a live session of Fedora 40, like from the same USB flash drive you used to install it?
(In reply to Nate Graham from comment #1) > The issue of the busy indicator being misplaced is Bug 488267. As for the > functional issue, does it *ever* find anything? Like, after, say, 30 > minutes? Or is it still stuck at that point? > > If so, does the issue reproduce in a new clean user account on the same > machine? > > If so, does the issue reproduce in a live session of Fedora 40, like from > the same USB flash drive you used to install it? I can reproduce the issue on both my installations, a desktop and a laptop. A newly created user is equally affected. I will try with a live session over the weekend.
I think I can reproduce the bug: 1. Launch Discover 2. *Immediately* search for something that should return no results (like "jfjlkdsjflkdsjf") It says "still looking" forever. Once it's in this state, all the next searches work properly. I also notice that only the first broken search suffers from Bug 488267; on subsequent searches, it's positioned correctly. Could be a clue.
For me timing doesn't matter. As long as the kns backend is loaded any invalid search never finishes.
*** Bug 490173 has been marked as a duplicate of this bug. ***