Created attachment 147193 [details] Discover error SUMMARY Ran Discover on my PinePhonePro, it reported there were updates which it applied (so I thought), on restarting and logging back in I got the error message in the screen shot STEPS TO REPRODUCE 1. Run Discover 2. Apply system updates 3. Restart OBSERVED RESULT Error screen displayed, the "Repair System" button appears to do nothing, the "Open Discover" button opens Discover, which tells me everything is up to date EXPECTED RESULT Updates applied, no error screen displayed SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Just wondering where I go to check what is failing and how I can resolve it.
Created attachment 147770 [details] failed update notification I can confirm this (see the attachment). This has repeatedly appeared and the repair button/open discover do nothing to resolve it. I believe Bug 451753 is also a duplicate.
I'm not sure there's much Discover can do there. This is PackageKit not applying the update properly. @David what distro are you on? Is it also Fedora?
No, Manjaro
I found a solution to the problem here (https://forum.manjaro.org/t/discover-system-updates-still-very-unreliable/110378) - long story short after I deleted the file /var/lib/PackageKit/offline-update-competed and restarted my PinePhone Pro no error message!
Same error popups on my Arch Linux KDE 5.27 after each offline-enabled update. It is possible to stop annoying popup by deleting "/var/lib/PackageKit/offline-update-competed" file. But after next offline update it appears again. There are no any errors with normal update (offline option is unchecked) neither with discover nor with pacman -Suy Help please! ========== > cat /var/lib/PackageKit/offline-update-competed ------------------ [PackageKit Offline Update Results] Success=false ErrorCode=failed-initialization ErrorDetails=failed to update database: unexpected system error
A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/527
Git commit e87a50f455619dea5c51dea9c290556739112fc7 by Nate Graham. Committed on 11/04/2023 at 20:53. Pushed by ngraham into branch 'master'. Always clear offline updates file after a repair operation No matter what the results of the repair operation were, there's nothing of any value that anyone can do with the file anymore, and if it sticks around, it can annoy the user on every subsequent login for no good reason. So let's just remove it. Related: bug 451753, bug 467638 FIXED-IN: 5.27.5 M +7 -0 libdiscover/backends/PackageKitBackend/PackageKitNotifier.cpp https://invent.kde.org/plasma/discover/commit/e87a50f455619dea5c51dea9c290556739112fc7
Git commit b18ebb137e49ccde3be49239bfaa8d88ace6a0c4 by Nate Graham. Committed on 11/04/2023 at 20:56. Pushed by ngraham into branch 'Plasma/5.27'. Always clear offline updates file after a repair operation No matter what the results of the repair operation were, there's nothing of any value that anyone can do with the file anymore, and if it sticks around, it can annoy the user on every subsequent login for no good reason. So let's just remove it. Related: bug 451753, bug 467638 FIXED-IN: 5.27.5 (cherry picked from commit e87a50f455619dea5c51dea9c290556739112fc7) M +7 -0 libdiscover/backends/PackageKitBackend/PackageKitNotifier.cpp https://invent.kde.org/plasma/discover/commit/b18ebb137e49ccde3be49239bfaa8d88ace6a0c4
Sorry, but I don't think this is resolved by Nate's patch. It would still produce the error after every upgrade, it will just be gone after pressing repair for subsequent reboots without an offline update. The bug is in the creation this error file for otherwise successful updates in the first place. $ sudo journalctl -b -1 -u packagekit-offline-update [...updates successfully...] Apr 23 14:11:48 hostname pk-offline-update[694]: percentage 91% Apr 23 14:11:48 hostname pk-offline-update[694]: percentage 95% Apr 23 14:11:48 hostname pk-offline-update[694]: percentage 100% Apr 23 14:11:48 hostname pk-offline-update[694]: status finished Apr 23 14:11:48 hostname pk-offline-update[694]: writing failed results Apr 23 14:11:49 hostname pk-offline-update[694]: failed to update system: failed to update database: Unerwarteter Systemfehler Apr 23 14:11:59 hostname pk-offline-update[694]: rebooting Apr 23 14:11:59 hostname systemd[1]: packagekit-offline-update.service: Deactivated successfully. Apr 23 14:11:59 hostname systemd[1]: Stopped Update the operating system whilst offline. $ sudo journalctl -b -1 -u packagekit Apr 23 14:11:07 hostname PackageKit[701]: daemon start Apr 23 14:11:07 hostname systemd[1]: Started PackageKit Daemon. Apr 23 14:11:07 hostname PackageKit[701]: uid 0 is trying to obtain org.freedesktop.packagekit.package-install-untrusted auth (> Apr 23 14:11:07 hostname PackageKit[701]: new update-packages transaction /1_debecaca scheduled from uid 0 Apr 23 14:11:07 hostname PackageKit[701]: uid 0 obtained auth for org.freedesktop.packagekit.package-install-untrusted Apr 23 14:11:07 hostname PackageKit[701]: Konnte Datei 'core.db' nicht von mirror.fra10.de.leaseweb.net übertragen : Could not > Apr 23 14:11:07 hostname PackageKit[701]: zu viele Fehlermeldungen von mirror.fra10.de.leaseweb.net, überspringe den Rest des V> Apr 23 14:11:07 hostname PackageKit[701]: Konnte Datei 'core.db' nicht von mirror.cmt.de übertragen : Could not resolve host: m> Apr 23 14:11:07 hostname PackageKit[701]: zu viele Fehlermeldungen von mirror.cmt.de, überspringe den Rest des Vorgangs Apr 23 14:11:07 hostname PackageKit[701]: Konnte Datei 'core.db' nicht von mirrors.xtom.de übertragen : Could not resolve host:> Apr 23 14:11:07 hostname PackageKit[701]: zu viele Fehlermeldungen von mirrors.xtom.de, überspringe den Rest des Vorgangs Apr 23 14:11:07 hostname PackageKit[701]: Konnte Datei 'core.db' nicht von mirror.selfnet.de übertragen : Could not resolve hos> Apr 23 14:11:07 hostname PackageKit[701]: zu viele Fehlermeldungen von mirror.selfnet.de, überspringe den Rest des Vorgangs Apr 23 14:11:07 hostname PackageKit[701]: Konnte Datei 'core.db' nicht von mirror.bethselamin.de übertragen : Could not resolve> Apr 23 14:11:07 hostname PackageKit[701]: zu viele Fehlermeldungen von mirror.bethselamin.de, überspringe den Rest des Vorgangs Apr 23 14:11:07 hostname PackageKit[701]: Abhängigkeits-Zyklus entdeckt: Apr 23 14:11:07 hostname PackageKit[701]: telepathy-kde-integration-module wird vor seiner Abhängigkeit telepathy-kde-common-in> Apr 23 14:11:07 hostname PackageKit[701]: unknown progress type 9 Apr 23 14:11:07 hostname PackageKit[701]: unknown progress type 9 Apr 23 14:11:07 hostname PackageKit[701]: unknown progress type 9 Apr 23 14:11:07 hostname PackageKit[701]: unknown progress type 9 [...continues to update succesfully...]
The creation is done by packagekit not discover.