SUMMARY After a recent Neon 5.27 package update (maybe a month or so ago) Discover started to throw up a dialog telling me "The PackageKit daemon has crashed" (cf. attached screenshot). This was reported to Discover a few times already but always closed as "please tell your Distro". Well, Neon is my distro, here you go. I actually doubt that this is a distro related issue since (a) it was reported for various distros (including Neon) (b) it started happening only after some KDE Neon package update (there might have been a PackageKit update involved though) STEPS TO REPRODUCE This is the way it happens to me: 1. Be notified about updates 2. Open Discover 3. Deselect the Neon packages, keep only the Flatpak updates 4. Press Apply or whatever that button is labeled with 5. A dialog will pop up telling you PackageKit has crashed 6. The Flatpak updates will actually suceed. At least it looks like that. OBSERVED RESULT A dialog "The PackageKit daemon has crashed" pops up EXPECTED RESULT No such dialog SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon User Edition 5.27 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION coredumpctl says: TIME PID UID GID SIG COREFILE EXE SIZE Mon 2023-10-30 13:22:59 CET 9575 0 0 SIGABRT inaccessible /usr/libexec/packagekitd n/a Mon 2023-10-30 13:23:00 CET 10331 0 0 SIGABRT inaccessible /usr/libexec/packagekitd n/a Mon 2023-10-30 14:02:58 CET 12922 0 0 SIGABRT inaccessible /usr/libexec/packagekitd n/a Wed 2023-11-01 09:01:55 CET 1656 0 0 SIGABRT inaccessible /usr/libexec/packagekitd n/a
Created attachment 162786 [details] Output of journalctl --boot | grep -i packagekit
Created attachment 162787 [details] Output of journalctl --boot -t systemd-coredump
Created attachment 162788 [details] Screenshot
It looks like this is a PackageKit bug indeed. Here is the Debian bug which resulted in this upstream fix which should then be backported for Neon (or maybe Discover should work around it): * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054026 * https://github.com/PackageKit/PackageKit/issues/656
I can reproduce this reliably by downgrading the zoom flatpak and updating it again.
I can confirm that I really often have this issue since quite a time. I don't like updating everything at the same time and most of my software are Flatpacks. (I'm also on KDE neon 5.27.9 and update through Discover.)