Summary: | After app is launched, first search for something that should return no results instead returns "Still looking" forever | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Massimiliano L <m.lincetto> |
Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | aleixpol, bugseforuns, nate, sitter |
Priority: | NOR | ||
Version: | 6.0.5 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=488267 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Massimiliano L
2024-06-08 08:46:59 UTC
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. *** |