SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. sudo pkcon update 2. 3. OBSERVED RESULT Fatal error: Error while installing package: 0.0000 EXPECTED RESULT Update done SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.13.0-28-generic #31~20.04.1-Ubuntu SMP Wed Jan 19 14:08:10 UTC 2022 x86_64 x86_64 x86_64 Operating System: KDE neon 5.24 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-28-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30,8 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION
Fixed by manually upgrading: 1988 sudo dpkg --configure -a 1989 sudo apt --fix-broken install 1990 sudo pkcon update 1991 sudo reboot But guys, surely pkcon can be smart enough to run this combo itself when broken??? Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.14.0-1024-oem (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30,8 GiB of RAM Graphics Processor: AMD RENOIR
Happened on KDE Neon. First try the error number was 42.??? or 47.??? I think (not sure), then 0.0000. sudo dpkg --configure -a sudo pkcon update was enough to fix it for me. Also https://old.reddit.com/r/kdeneon/comments/t51rnr/pkcon_update_then_fatal_error_error_while/
I've had the same issue. I've tried sudo dpkg --configure -a sudo pkcon update like you suggested and the latter command is stuck at "65%" progress since around 15 minutes. Is that normal? I can see that pkcon uses 100% of one CPU-core continuously so something might be happening (?).
That seems to be normal. PKCON is sometimes stuck at the same % point for tens of minutes. Again something that is hardly user friendly.
Thanks a lot for the quick answer. Yes, I have experienced similar things in the past as well, otherwise I would've killed the process long ago. It's still running now at 65%. So I'll wait I guess! Thanks again.
I also got the same error after running “sudo pkcon update”. It was after a failure in system updates using Discover; but being an inexperienced user of Linux, I didn't know this was what caused the system update failure. I performed a clean installation because I didn't know how else to fix it 😞 Totally agree with what you said that pkcon should run those commands itself in case of such error. It will indeed benefit novice users that fix the error themselves.
I experienced this bug as well. I attemped to update with KDE Discover and it failed. I was also able to update using the dkpg command however now every time I start my computer, KDE Discover still shows me the broken notification. "Error while installing package: 0.0000" How did you guys resolve this?
After the dpkg command, did you also do sudo pkcon update ? For me that was enough.
Yes I did a sudo pkcon update right away. The problem now is that KDE Discover is out of sync with pkcon now. It tells me the update failed every time when actually it did not fail. I get the notification every time I boot. Is there a way to clear the notification out or to get KDE discover back in sync with the package management system?
Yes, there is a way to get rid of the notification. I don't remember exactly how, but I did it as well. Probably somewhere in system settings. I'm also hiding the "updates" icon in the task bar (the up-arrow with two arrows in circles around it) by default, so I don't even see the little blue or red dot on it when there are updates available. About getting Discover back in sync with the package management system, all I can say is that sometimes it helps to just wait. One of the next times you install updates (manually), the problem will hopefully be gone. I know this answer isn't so satisfying, but after years of using KDE Plasma, I unfortunately had to adopt such strategies..
Interesting, one of the reasons why I moved from Gnone to KDE was because the Gnone updater app I tried in Debian,Fedora and Ubuntu, whatever the equivalent of KDE Discover is, would break just about every other time I tried to use it. I spend hours trying to get it to work and finally threw in the towel and just used the command line. Up until this point the KDE Discover app has "just worked". It reliably updated my system every time, it was one component I never had to worry about until now. It is sad to see the same thing is happening to KDE.
Thank you for your bug report! However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since before 01/01/2025. Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's. Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report. Thanks for understanding!