Bug 513393

Summary: Discover Flatpak source list is broken for me
Product: [Applications] Discover Reporter: pollux/ned <pollux66>
Component: discoverAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aleixpol, olib141
Priority: NOR    
Version First Reported In: 6.5.4   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Sources flatpak list looking broken

Description pollux/ned 2025-12-15 12:25:58 UTC
Created attachment 187662 [details]
Sources flatpak list looking broken

SUMMARY
Had some KDE framework updates and noticed discover flatpak source list looks broken now for me lol

STEPS TO REPRODUCE
1. Be on KDE Framework 6.21
2. Check Discover settings source flatpak list
3. Should see the list looking broken

OBSERVED RESULT
Flatpak source list looks broken

EXPECTED RESULT
For it not look broken, i can still use tho lol

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Cachyos
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
Comment 1 pollux/ned 2025-12-15 12:27:10 UTC
Log of opening discover
plasma-discover
libs QList("/usr/lib/qt6/plugins", "/usr/bin")
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
org.kde.plasma.libdiscover: error loading "packagekit-backend" "Cannot load library /usr/lib/qt6/plugins/discover/packagekit-backend.so: libpackagekitqt6.so.2: cannot open shared object file: No such file or directory" QJsonObject({"IID":"org.kde.discover.6.5.4.AbstractResourcesBackendFactory","archlevel":4,"className":"PackageKitBackendFactory","debug":false,"version":395776})
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Comment 2 Oliver Beard 2025-12-15 13:29:41 UTC
Fixed with https://invent.kde.org/frameworks/kirigami/-/merge_requests/1990.
Comment 3 Oliver Beard 2025-12-15 13:46:41 UTC

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