Bug 433151 - Refreshing KickOff's application list twice without changing the category empties the right view
Summary: Refreshing KickOff's application list twice without changing the category emp...
Status: RESOLVED DUPLICATE of bug 433119
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) widget (show other bugs)
Version: 5.21.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-18 10:44 UTC by Reiddragon
Modified: 2021-02-18 15:39 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
KickOff with an empty right view (94.10 KB, image/png)
2021-02-18 10:44 UTC, Reiddragon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Reiddragon 2021-02-18 10:44:22 UTC
Created attachment 135832 [details]
KickOff with an empty right view

SUMMARY
Refreshing KickOff's application list twice without changing the category empties the right view

STEPS TO REPRODUCE
1. open KickOff and keep it open (inside plasmoidviewer or add it to the desktop)
2. update the application list twice without changing the category (in my testing I removed and readded the same icon to ~/.local/share/applications, waiting for Kwin to refresh the application list in between)

OBSERVED RESULT
KickOff's right view just goes empty, changing categories fixes it however

EXPECTED RESULT
KickOff should just update the view, adding/removing the icons regardless of how many refreshes there are in the application list

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 The Feren OS Dev 2021-02-18 13:27:19 UTC
I can reproduce this and was gonna show it off in the Telegram chat later today.
Comment 2 The Feren OS Dev 2021-02-18 15:20:07 UTC
Demonstrated the bug in this video:
https://www.youtube.com/watch?v=Wl5gzc2wVd4
Comment 3 Nate Graham 2021-02-18 15:39:40 UTC
Seems like the same root cause as Bug 433119.

*** This bug has been marked as a duplicate of bug 433119 ***