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 refresh && sudo pkcon update -y 2. 3. OBSERVED RESULT Fatal error: The following packages have unmet dependencies: libpoppler-qt5-1: Depends: libpoppler126 (= 23.03.0-0xneon+22.04+jammy+release+build11) but 23.02.0-0xneon+22.04+jammy+release+build10 is to be installed okular-backends: Depends: libokular5core10 (= 4:22.12.2-0xneon+22.04+jammy+release+build19) but 4:22.12.3-0xneon+22.04+jammy+release+build20 is to be installed libpoppler-cpp0v5: Depends: libpoppler126 (= 23.03.0-0xneon+22.04+jammy+release+build11) but 23.02.0-0xneon+22.04+jammy+release+build10 is to be installed poppler-utils: Depends: libpoppler126 (= 23.03.0-0xneon+22.04+jammy+release+build11) but 23.02.0-0xneon+22.04+jammy+release+build10 is to be installed libpoppler-glib8: Depends: libpoppler126 (= 23.03.0-0xneon+22.04+jammy+release+build11) but 23.02.0-0xneon+22.04+jammy+release+build10 is to be installed EXPECTED RESULT A successful update of packages. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5 CPU M 520 @ 2.40GHz Memory: 7.6 GiB of RAM Graphics Processor: NVA8 Manufacturer: LENOVO Product Name: 43142MU System Version: ThinkPad T510 ADDITIONAL INFORMATION Thanks!
Same error
a new package has just been produced in release which links to the correct version of libpoppler*. it will be promoted to user in the next few days.
(In reply to Carlos De Maine from comment #2) > a new package has just been produced in release which links to the correct > version of libpoppler*. it will be promoted to user in the next few days. Thank you!
(In reply to Carlos De Maine from comment #2) > a new package has just been produced in release which links to the correct > version of libpoppler*. it will be promoted to user in the next few days. Hi. This is still going on. When is "the next few days"? Where can I see the releases & updates? Do I need to do anything else to fix the broken packages? Thank you!
(In reply to Eric R from comment #4) > (In reply to Carlos De Maine from comment #2) > > a new package has just been produced in release which links to the correct > > version of libpoppler*. it will be promoted to user in the next few days. > > Hi. This is still going on. When is "the next few days"? > Where can I see the releases & updates? > Do I need to do anything else to fix the broken packages? > Thank you! Tried 30 minutes ago, everything passed and no packages held back anymore! Although, couldn't fix it with pkcon update, but instead with apt upgrade
When will the update be ready? Thanks
jriddel rolled a new release. they should be in user now.
(In reply to Carlos De Maine from comment #7) > jriddel rolled a new release. they should be in user now. pkcon update don't work for me...
Hi. sudo pkcon refresh && sudo pkcon update -y now produces: Fatal error: The following packages have unmet dependencies: libokular5core10: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed Depends: libqt5printsupport5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed drkonqi-pk-debug-installer: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed qt5-gtk-platformtheme: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed okular-backends: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed Depends: libqt5printsupport5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed gwenview: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed Depends: libqt5printsupport5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed qtwayland5: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed Depends: libqt5waylandclient5 (>= 5.15.8+p22.04+tunstable+git20230310.0045) but 5.15.8+p22.04+tunstable+git20230304.0049-0 is to be installed libqt5waylandcompositor5: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed libqt5widgets5: Depends: libqt5gui5 (>= 5.15.8+p22.04+tunstable+git20230309.0057) but 5.15.8+p22.04+tunstable+git20230209.0323-0 is to be installed okular-dbgsym: Depends: okular (= 4:22.12.3-0xneon+22.04+jammy+release+build22) but 4:22.12.2-0xneon+22.04+jammy+release+build19 is to be installed okular: Depends: libokular5core10 (= 4:22.12.2-0xneon+22.04+jammy+release+build19) but 4:22.12.3-0xneon+22.04+jammy+release+build22 is to be installed okular-extra-backends: Depends: libokular5core10 (= 4:22.12.2-0xneon+22.04+jammy+release+build19) but 4:22.12.3-0xneon+22.04+jammy+release+build22 is to be installed So I suppose the original problem is fixed, but now there are other broken packages. sudo apt update && sudo apt dist-upgrade upgrades other packages, but the broken packages are still broken. I also tried this: sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done 0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded. What else should I try? Thanks!
Matija said in comment #5 in this thread that apt worked rather than pkcon. https://bugs.kde.org/show_bug.cgi?id=466862#c5
also try: sudo apt install libturbojpeg then sudo apt install libjpeg8
(In reply to Carlos De Maine from comment #11) > also try: > sudo apt install libturbojpeg > then > sudo apt install libjpeg8 last thing to try after that is doing `sudo apt full-upgrade`
(In reply to Matija from comment #12) > (In reply to Carlos De Maine from comment #11) > > also try: > > sudo apt install libturbojpeg > > then > > sudo apt install libjpeg8 > > last thing to try after that is doing `sudo apt full-upgrade` also, does Discover work for you guys after this or it hangs on "Loading..." when on home screen of the app?
(In reply to Matija from comment #12) > (In reply to Carlos De Maine from comment #11) > > also try: > > sudo apt install libturbojpeg > > then > > sudo apt install libjpeg8 > > last thing to try after that is doing `sudo apt full-upgrade` After: sudo apt install libturbojpeg sudo apt install libjpeg8 sudo apt full-upgrade total disaster, it's gone Dolphin, Discover, Konsole and other app. What the fuck is that?, what do I do now????
(In reply to Al from comment #14) > (In reply to Matija from comment #12) > > (In reply to Carlos De Maine from comment #11) > > > also try: > > > sudo apt install libturbojpeg > > > then > > > sudo apt install libjpeg8 > > > > last thing to try after that is doing `sudo apt full-upgrade` > > After: > sudo apt install libturbojpeg > sudo apt install libjpeg8 > sudo apt full-upgrade > > total disaster, it's gone Dolphin, Discover, Konsole and other app. What the > fuck is that?, what do I do now???? I was able to repair the system by reinstalling: kgamma5 kde-config-screenlocker bluedevil plasma-workspace-wayland rint-manager plasma-widgets-addons plasma-welcome plasma-wallpapers-addons plasma-vault plasma-runners-addons plasma-pa plasma-nm plasma-firewall plasma-disks plasma-dataengines-addons plasma-calendar-addons plasma-browser-integration kwin-addons ksshaskpass kscreen kio-admin kdialog kdegraphics-thumbnailers kde-spectacle drkonqi-pk-debug-installer flatpak-kcm kde-nomodeset kde-inotify-survey kde-config-sddm kde-config-plymouth kde-config-gtk-style dophin dolphin-plugins ark sddm-theme-breeze kio-gdrive I don't understand what happened!! I keep seeing the message "Loading..."
*** Bug 466957 has been marked as a duplicate of this bug. ***
i prefer apt dist-upgrade as it lets you review what packages it installs and removes and asks for your confirmation before doing anything, sudo apt install --install-recommends plasma-desktop neon-desktop should also bring back it to a normal install
(In reply to Carlos De Maine from comment #17) > i prefer apt dist-upgrade as it lets you review what packages it installs > and removes and asks for your confirmation before doing anything, > > sudo apt install --install-recommends plasma-desktop neon-desktop > > should also bring back it to a normal install Carlos, This seems to have gone from a couple of broken packages to a BUNCH of broken packages and even unusable systems for a lot of users, according to what I'm seeing here, in the KDE forums, and on Reddit. So I wonder now, is this still the same bug, or should there be a new bug? Is this perhaps fixed at the repo/dev end, but now users just need to clean up broken packages? Just trying to figure out what to do next, for myself and other users who seem to have this same problem. I haven't tried your latest suggestions yet, because I'm waiting to see if there is any other movement on this. Thanks, Eric
It's a new bug due to libharfbuzz0b not having an i386 build. I've removed harfbuzz now and will snapshot once tested
(In reply to Jonathan Riddell from comment #19) > It's a new bug due to libharfbuzz0b not having an i386 build. I've removed > harfbuzz now and will snapshot once tested Everything is solved Thanks!
Hello, Jonathan Riddell yesterday I managed to solve most of my problems by uninstalling several 32bit packages (related to wine and lutris and some installed by Steam) and then running again the sudo pkcon update https://gist.github.com/luzfcb/5c323433b980d79aa1597f9bd32a0b2f Today pkcon informs me that support for HP printers and other applications will be removed so that it will be possible to downgrade some libraries The fact is: I'm afraid if I run this, it will break even more, and I'll have another round of crashing packets. Since this machine is also the machine I use for work, I was wondering whether or not this downgrade is expected to occur and if i can go ahead and update ❯ sudo pkcon update Getting updates [=========================] Finished [=========================] Testing changes [=========================] Finished [ ] (0%) The following packages have to be removed: flowblade-2.8.0.3-3.all non-linear video editor hplip-3.21.12+dfsg0-1.amd64 HP Linux Printing and Imaging System (HPLIP) libharfbuzz-subset0-6.0.0+dfsg-3+22.04+jammy+release+build1.amd64 OpenType text shaping engine (subset library) libraqm-dev-0.10.0-0xneon+22.04+jammy+release+build13.amd64 Development files for Raqm library libraqm0-0.10.0-0xneon+22.04+jammy+release+build13.amd64 Library for complex text layout lutris-0.5.11.all video game preservation platform python3-matplotlib-3.5.1-2build1.amd64 Python based plotting system in a style similar to Matlab (Python 3) python3-pil-9.0.1-1ubuntu0.1.amd64 Python Imaging Library (Python3) python3-pil.imagetk-9.0.1-1ubuntu0.1.amd64 Python Imaging Library - ImageTk Module (Python3) python3-reportlab-3.6.8-1.all ReportLab library to create PDF documents using Python3 The following packages have to be downgraded: gir1.2-harfbuzz-0.0-2.7.4-1ubuntu3.1.amd64 OpenType text shaping engine (GObject introspection data) libharfbuzz-dev-2.7.4-1ubuntu3.1.amd64 Development files for OpenType text shaping engine libharfbuzz-gobject0-2.7.4-1ubuntu3.1.amd64 OpenType text shaping engine ICU backend (GObject library) libharfbuzz-icu0-2.7.4-1ubuntu3.1.amd64 OpenType text shaping engine ICU backend libharfbuzz0b-2.7.4-1ubuntu3.1.amd64 OpenType text shaping engine (shared library) Proceed with changes? [N/y]
(In reply to Jonathan Riddell from comment #19) > It's a new bug due to libharfbuzz0b not having an i386 build. I've removed > harfbuzz now and will snapshot once tested I agree, this is now fixed for me. I did "sudo pkcon refresh" and it looked like a normal refresh. So far, so good. I did "sudo pkcon update" and I had a look at what it wanted to update. This time, it didn't want to delete anything, just update a bunch of packages. So I hit "Y" and let it run. Then I rebooted. Everything looks fine now. I don't think I'll blindly do "sudo pkcon refresh && sudo pkcon update -y" any more, though. I'm going to pay attention to what pkcon has to tell me before I let it proceed! As far as I'm concerned, this bug can be closed. Thanks to everyone who worked on this, and on ALL of KDE!