SUMMARY In Kickoff (app launcher), when switching from an application section to another, there can be "leftover" entry from previous section, that doesn't belong to current section. STEPS TO REPRODUCE 1. Have an application section that have many entries, that needs scrolling to reach all. For example, "All Applications". 2. (Mouse) hover that section, in the shown section list, scroll down some entries. (in my case, that's more than 8) 3. Hover another section, inside see what's the first entry. OBSERVED RESULT The first entry (of current section) is (or have great chance to be) replaced by one from the previous section, that (probably) is the last being hidden (internally) by scrolling. EXPECTED RESULT The first entry just being of current section. SOFTWARE/OS VERSIONS Operating System: Artix Linux x86_64 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.4-artix1-1 (64-bit) Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION Actually this problem is always there for a long time (at least months, when I started using the "new" kickoff layout), and on many Distros (at least KDE neon, Manjaro, and Artix), on both of my computers and a virtual machine. Though I've gathered how to correctly reproduce just now. It could just be "fixed" by hovering on another section (without scrolling) then back. But that's yet extra time.
Cannot reproduce. Could you maybe attach a screen recording that shows the issue happening? That would be helpful. Thanks!
Created attachment 148416 [details] How "leftover" entry happens to be there A screen record in Webm format, showing how "leftover" entry happens to be in Kickstart menu
You are just hovering on items and then changing categories, right? I can't reproduce either.
Oh, I missed the bit about scrolling down a ways. Now I can reproduce it. It seems to be a visual bug since if I click on the entry, it still opens the app that should have been there. Maybe something is being cached somewhere? Maybe the index for something is failing to update?
*** This bug has been marked as a duplicate of bug 445512 ***