Bug 501427 - kickoff search shows distro packages even when the packagekit discover backend is not present
Summary: kickoff search shows distro packages even when the packagekit discover backen...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: PackageKit (other bugs)
Version First Reported In: master
Platform: KDE Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-12 19:29 UTC by renner0
Modified: 2025-03-12 23:44 UTC (History)
2 users (show)

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


Attachments
kde linux discover missing backend (740.49 KB, image/png)
2025-03-12 19:29 UTC, renner0
Details

Note You need to log in before you can comment on or make changes to this bug.
Description renner0 2025-03-12 19:29:26 UTC
Created attachment 179356 [details]
kde linux discover missing backend

SUMMARY
When you remove the package plasma-discover-rpm-ostree on Fedora Kinoite or use an atomic version of Fedora like Bazzite or just use KDE Linux

STEPS TO REPRODUCE
1. use a system that does not ship a backend for distro packages, only a backend of flatpak is present (KDE Linux, Bazzite)
2. search for kmail in kickoff (any application not available on flathub but in distro repos)
3. click on kmail search result

OBSERVED RESULT
discover opens with the following error message

Could not open appstream://org.kde.kmail2.desktop because it
was not found in any available software repositories.

EXPECTED RESULT
Don't show search results for stuff you can't install

SOFTWARE/OS VERSIONS
Could not open appstream://org.kde.kmail2.desktop because it
was not found in any available software repositories.

Operating System: KDE Linux 202503120255
KDE Plasma Version: 6.3.80
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Comment 1 Harald Sitter 2025-03-12 23:03:47 UTC
That doesn't really have anything to do with the packagekit backend, but the appstream data. What happens is that as long as the appstream data is available (e.g. because of a package that provides the files in /usr/share/swcatalog) we still know this application exists. We don't know that it doesn't actually have any available sources until we load all backends though. So, in a way this is an integration bug. If the thing that provides the appstream data is no longer able to install the packages it should remove the appstream data.

That is for example what happens with flatpak. We have the appstream data attached to the remote and if you remove e.g. flathub then it takes its appstream data with it and we won't enumerate applications that cannot be installed.

https://invent.kde.org/kde-linux/kde-linux/-/issues/162
Comment 2 renner0 2025-03-12 23:44:59 UTC
Thanks for the clarification!