SUMMARY I've noticed that in the PackageKit plugin, it is specifically hardcoded to deny it from being used when /run/ostree-booted exists. https://invent.kde.org/plasma/discover/-/blob/master/libdiscover/backends/PackageKitBackend/PackageKitBackend.h#L90 I have recently written a PackageKit backend to specifically support bootc-based images for updating over PackageKit (https://github.com/FyraLabs/PackageKit-bootc), and Discover refuses to start and crashes outright, considering the plugin invalid due to /run/ostree-booted existing, making updates over PackageKit impossible. STEPS TO REPRODUCE 1. Install PackageKit-bootc and the PackageKit backend 2. Attempt to run Plasma Discover OBSERVED RESULT The PackageKit backend gets rejected and the application crashes EXPECTED RESULT Discover loads the PackageKit backend SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Ultramarine Linux 43 KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 ADDITIONAL INFORMATION
If you remove that check, does everything work?
(In reply to Nate Graham from comment #1) > If you remove that check, does everything work? Yes, reverting commit b7ed897e6842002b195c02c6e89f4e06aee12d09 (https://invent.kde.org/plasma/discover/-/commit/b7ed897e6842002b195c02c6e89f4e06aee12d09), and using the new PackageKit bootc plugin, everything works as intended.
Are you interested in sending a merge request to change that?
(In reply to Nate Graham from comment #3) > Are you interested in sending a merge request to change that? Yes, I will do that soon