Bug 471891

Summary: Installing an app when Kickoff is open clears the visible category
Product: [Plasma] plasmashell Reporter: esperluette08
Component: Application Launcher (Kickoff) widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: minor CC: bugseforuns, cwo.kde, mikel5764, nate, noahadvs
Priority: NOR    
Version First Reported In: 5.27.5   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=481855
Latest Commit: Version Fixed/Implemented In: 6.4.0
Sentry Crash Report:

Description esperluette08 2023-07-03 03:29:27 UTC
SUMMARY
When installing a new app (like from "apt") when Kickoff is open, the app grid becomes empty when the installation is finished. 

STEPS TO REPRODUCE
1. (Re-)Install for example Firefox ("apt install -y firefox")
2. Open Kickoff and select "Internet" category before the installation is finished

OBSERVED RESULT
Once the installation is finished, the applications grid is empty. Changing the category, or re-opening Kickoff, displays correctly the grid with Firefox installed.

EXPECTED RESULT
The application grid should be not become empty, and the newly application should appear in the relevant category without having to change category or to close then re-open Kickoff.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon Live (20230504-0714)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Graphics: X11 on Neon
Comment 1 Nate Graham 2023-09-12 20:03:07 UTC
Can reproduce. Presumably because kbuildsycocoa5/6 triggers a refresh and the view doesn't re-populate afterwards.
Comment 2 Patrick Silva 2024-03-15 13:44:41 UTC
I noticed this behavior on my Arch Linux a few days ago when using Kickoff while installing updates with pacman.

Operating System: Arch Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Graphics Platform: Wayland
Comment 3 Nate Graham 2024-03-18 18:14:23 UTC
Can also still reproduce, even after Bug 481855 was fixed. Perhaps a similar change needs to be applied here.
Comment 4 cwo 2025-06-08 14:37:26 UTC
Likely the same cause as bug 504891 and I can't reproduce this anymore with the fix to that bug applied. If it still happens in 6.4, please reopen.