Discover reported failed updates and offered a button Repair. It than said Repair failed. I cannot provide more info because Discover didn’t.
What is the state of Discover?
On what distro?
Also, what failed to update, repo packages?
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
Qt Version: 6.11.2
Kernel Version: 7.1.13-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX Vega
I don’t know what failed to update as discover isn’t telling that either. I just switched on my workstation, Fedora went through an update, KDE Plasma came on and Discover popped up reporting an error
Have you reported the issue to Fedora?
It probably should be triaged there first. Discover is using PackageKit to update repo packages and that integration could be the thing that is failing.
Fedora says it is KDE. Are they on speaking terms or not really?
It is failing to load libdnf, that is definitely something I would report to Fedora.
Yes, where were you told to report it to KDE?
Perhaps this is something?
$ plasma-discover
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
adding empty sources model QStandardItemModel(0x55fa4536ecc0)
qrc:/qt/qml/org/kde/discover/qml/DiscoverWindow.qml:127:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15.
Use 'sequences: \[ <key> \]' to bind to all of them.
qt.qml.propertyCache.append: Member focusPolicy of the object CarouselPageIndicator_QMLTYPE_420 overrides a member of the base object. Consider ren
aming it or adding final or override specifier
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection alrea
dy associated with an application ID")
fwupd: Device not supported: UEFI dbx No releases found
qrc:/qt/qml/org/kde/discover/qml/UpdatesPage.qml:40:5: QML OverlaySheet: Binding loop detected for property "y":
qrc:/qt/qml/org/kde/kirigami/templates/OverlaySheet.qml:121:5
packagekitqt.offline: Properties could not be invalidated "org.freedesktop.PackageKit.Offline" QList("PreparedUpgrade")
packagekitqt.offline: Properties could not be invalidated "org.freedesktop.PackageKit.Offline" QList("PreparedUpgrade")
packagekitqt.offline: Properties could not be invalidated "org.freedesktop.PackageKit.Offline" QList("PreparedUpgrade")
packagekitqt.offline: Properties could not be invalidated "org.freedesktop.PackageKit.Offline" QList("PreparedUpgrade")
QIODevice::read (QSslSocket): device not open
this didn´t help sudo dnf distro-sync --refresh --releasever=44 --allowerasing --setopt=protected_packages=
Discover is still reporting failed with zero clue why. Report errors without a user being able to know why let alone repari is a bug
if you create a new user acct, does discover work properly from there?
did it again.
Where does Discover file or log what has failed and why? If it writes to stderr, which it might what is the binary Discover called?
It’s called plasma-discover and files this when started:
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true
adding empty sources model QStandardItemModel(0x561b0fac7d30)
qrc:/qt/qml/org/kde/discover/qml/DiscoverWindow.qml:127:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use '
sequences: \[ <key> \]' to bind to all of them.
qt.qml.propertyCache.append: Member focusPolicy of the object CarouselPageIndicator_QMLTYPE_347 overrides a member of the base object. Consider renaming
it or adding final or override specifier
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already ass
ociated with an application ID")
fwupd: Device not supported: Intel Management Engine is not updatable
\*\* (process:6212): **WARNING** \*\*: 17:14:53.925: Found icon of unknown type 'unknown' in 'system/package/os/ee.ria.qdigidoc4/\*', skipping it.
\*\* (process:6212): **WARNING** \*\*: 17:14:53.926: Found icon of unknown type 'unknown' in 'system/package/os/org.kde.discover.flatpak/\*', skipping it.
\*\* (process:6212): **WARNING** \*\*: 17:14:53.929: Found icon of unknown type 'unknown' in 'system/package/os/org.kde.discover.snap/\*', skipping it.
\*\* (process:6212): **WARNING** \*\*: 17:14:53.952: Found icon of unknown type 'unknown' in 'system/package/os/io.github.syllo.nvtop/\*', skipping it.
\*\* (process:6212): **WARNING** \*\*: 17:14:54.048: Found icon of unknown type 'unknown' in 'system/package/os/org.kde.mobile.plasmasettings/\*', skipping it.
\*\* (process:6212): **WARNING** \*\*: 17:14:54.114: Found icon of unknown type 'unknown' in 'system/package/os/im.dino.Dino/\*', skipping it.
\*\* (process:6212): **WARNING** \*\*: 17:14:54.382: Found icon of unknown type 'unknown' in 'system/package/os/org.kde.kiten.desktop/\*', skipping it.
\*\* (process:6212): **WARNING** \*\*: 17:14:54.624: Found icon of unknown type 'unknown' in 'system/package/os/org.deepin.calendar/\*', skipping it.
QIODevice::read (QSslSocket): device not open
discover itself dumps to the terminal when u launch plasma-discover. repair fail usually sits in packagekit / dnf under it.
-journalctl --user -b | rg -i ‘discover|packagekit|libdnf’
-journalctl -u packagekit -b --no-pager | tail -80
-sudo pkcon -v get-updates
-sudo dnf check
if libdnf wont load like dalto said thats a fedora packagekit-dnf thing. paste those logs on a fedora bug.