Bug 458815 - Apps are missing their context menus' "Manage or uninstall addons" items if their AppStream ID doesn't match their .desktop file name
Summary: Apps are missing their context menus' "Manage or uninstall addons" items if t...
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-06 20:22 UTC by Nate Graham
Modified: 2022-09-07 18:57 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2022-09-06 20:22:46 UTC 
This menu item is shown if the app is detected to have an AppStream ID, which we find by looking for AppStream components that match its .desktop file name in actionlist.cpp (https://invent.kde.org/plasma/plasma-workspace/-/blob/master/applets/kicker/plugin/actionlist.cpp#L433).

This produces false negatives because the .desktop fie name and the AppStream ID don't have to match and this is a perfectly valid state of affairs. When this happens, the app's context menu in Kicker, Kickoff, and Dashboard is missing the "Manage or uninstall addons" menu item.

This affects for example System Monitor, whose desktop file name is org.kde.plasma-systemmonitor.desktop, but its AppStream ID is org.kde.plasma.systemmonitor.

We should find a more robust way of getting an app's AppStream ID, since assuming it matches the name of the .desktop file is not reliable.
Comment 1 Nate Graham 2022-09-06 20:23:05 UTC 
Fixing this would also generically fix Bug 458812.
Comment 2 Nate Graham 2022-09-07 17:05:47 UTC 
This was traced to an upstream bug: https://github.com/ximion/appstream/issues/431.
Comment 3 Nicolas Fella 2022-09-07 18:45:48 UTC 
Narrator: It was not an upstream bug
Comment 4 Nate Graham 2022-09-07 18:57:20 UTC 
In fact the originally reported bug itself was faulty.