Bug 460989 - pkcon returning error 0.0000 and libkf5plasmaquick5 broken
Summary: pkcon returning error 0.0000 and libkf5plasmaquick5 broken
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-25 16:12 UTC by me
Modified: 2025-09-20 09:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot of the terminal with my attempts at figuring this out (197.06 KB, image/png)
2022-10-25 16:12 UTC, me
Details

Note You need to log in before you can comment on or make changes to this bug.
Description me 2022-10-25 16:12:02 UTC
Created attachment 153198 [details]
Screenshot of the terminal with my attempts at figuring this out

SUMMARY
I'm running KDE neon User edition and I wanted to update some packages, but Discover fails without telling me, so it asks me to update and reboot indefinitely. When I try to update on the command line with pkcon, I get error 0.0000. After some research I find out that the libkf5plasmaquick5 package is broken and if I try to reinstall it apt will just give me a dpkg error code 1.


STEPS TO REPRODUCE
1. Update via Discover or the command line
2. Try to reinstall libkf5plasmaquick5 

OBSERVED RESULT
Non descriptive errors.

EXPECTED RESULT
Updates should work.

SOFTWARE/OS VERSIONS
Linux: KDE neon 5.26
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.99
Qt Version: 5.15.6

ADDITIONAL INFORMATION
This is running in a KVM.
Comment 1 Carlos De Maine 2025-09-20 09:35:32 UTC
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!