Bug 508724

Summary:	Application menu suddenly won't show new entries without logout/login or other force-refresh
Product:	[Plasma] plasmashell	Reporter:	DarthZiplock <offrhode92>
Component:	Application Menu (Kicker) widget	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	6.4.4
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description DarthZiplock 2025-08-25 16:19:07 UTC

SUMMARY
This began happening out of the blue yesterday. After installing a new app via Discover, DNF, or PWA, the application entry no longer automatically appears in the Application Menu widget. It does appear in the application entries editor. To get it to show up in the widget requires some method of force-refreshing, such as logging out and back in, changing widget types, or editing something in the "Edit Applications" app and saving changes.

STEPS TO REPRODUCE
1.  Install something from Discover
2.  See that it's not present in the Application Menu
3.  Confirm that it exists in Application Editor, and force the widget to refresh/reload somehow

OBSERVED RESULT
New applications do not appear in Application Menu without a force refresh/reload

EXPECTED RESULT
New applications should appear automatically in Applications Menu as they previously did

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Fedora 42
KDE Plasma Version:  6.4.4
KDE Frameworks Version:  6.17.0
Qt Version:  6.9.1

ADDITIONAL INFORMATION
Rebooting doesn't seem to help. This just randomly became a problem after several weeks of flawless use post-install.

Comment 1 Nate Graham 2025-08-26 20:05:31 UTC

Does the same thing happen in a new clean user account on the same computer?

Comment 2 DarthZiplock 2025-09-01 02:35:24 UTC

(In reply to Nate Graham from comment #1)
> Does the same thing happen in a new clean user account on the same computer?

Never got a chance to try. A few reboots didn't fix it, but some system updates did. Must've just been a case of wonked permissions on the cache.

Comment 3 Nate Graham 2025-09-01 21:53:23 UTC

OK great, thanks.