Today I got a notification that there’s an upgrade to KDE neon 24.04.1 LTS, but the tray icon just shows the message in the title on clicking it. Whenever I run apt upgrade , I see it has kept back libpoppler-glib8 from being upgraded, and maybe that’s causing the issue.
What do I do?
First, before you do anything super major, you should make a backup of your drive. That’s what you should do.
After reading this, I’m glad I am not in a rush. Still on 22.04.
You should make a backup of your drive when these huge upgrades are available (that can literally prevent you from reaching your desktop on boot). I even say the same thing to Windows users; as much as some Windows users love to gloat about Windows being perfect with no issues (despite being proven that Microsoft is also prone to release botched system upgrades).
Always assume huge upgrades like these will cause problems. I use RescueZilla (CloneZilla with a GUI) to make an entire backup of the drive.
And then, to test if it works, restore that backup to a virtual machine to test if the update will fail, causing the system to break. Or even use an older iso image to load KDE Neon with the previous Ubuntu base. Then try upgrading it.
I do this as a fail safe (and so that I never have any system down time). I’ve learned my lesson when I upgraded from 16.04 to 18.04 at the time.
BTW, I’ve been sitting with the same installation of KDE Neon since 18.04 
PS: I keep my OS drive small. So, it’s much easier to backup and restore. Another thing; never keep your important files on the same partition as the OS.
I would suggest you to remove this package, and whatever depends on it, upgrade and install again what what using it.
Neon will always have packages incompatibilities creeping in due to its ubuntu LTS base.
And use pkcon to update neon.
That was scary! I have 2 separate physical drives and my home partition is on the second one so I can reinstall the OS without problems. I have a Slimbook laptop that came with Neon 6.2 preinstalled.
It’s got a zillion things dependent on it including Wine, unfortunately 
apt suggests I remove everything that depends on it as well.
That is probably the main reason, i would guess all other things just need a libpoppler-glib8 version (the newer one that is usually provided with / alongside KDE should be fine) but WINE needs the “special” Ubuntu version of it or fail.
The usual install instruction, I remember, for WINE on, not Ubuntu itself but, Ubuntu based Distros is “downgrade” to the specific ubuntu (only) provided version and prevent it from updating.
It’s beyond me how WineHQ dragged that issue for more than 2 years over several versions. But they support Ubuntu (only) I guess 
.
Otherwise what dreaperxz said, make sure to have a backup.
Same situation, gonna gut the packages and then upgrade and reinstall em, seems to be the only course.
Will report success, or a reinstall…
Edit:
Removing libpoppler, then reinstalling wine-staging got me here. with an updated libpoppler to boot.
Edit Edit:
Upgrade finished booted into “Oh no! something has gone wrong”
logging into another session got me in, so not all is lost.
Beware the upgrade…
All good in terms of the upgrade; I removed lib-poppler-glib8 and it went off smoothly. Except that now wine appears broken for good and the one packaged with Ubuntu doesn’t cut it for 64 bit prefixes.
This is why I use Flatpak applications mostly now; to avoid having broken packaging (especially when big upgrades come out). This way, none of my applications are touched other than mainly the applications that come with a base KDE Neon install.
I even use Flatpak versions of Lutris and Bottles and let those tools download wine. This is so that wine is completely separate from the OS itself. And what’s great about it is that I can have various versions of wine at my disposal.
Anyway, I made a backup of my SSD that Neon is running off of. I restored the image to a virtual machine. Then I upgraded it in the VM as a test.
I have to say that after that test, it’s still a rough upgrade process. The upgrading tool still had issues. And when it finished, it errored out and locked up.
Surprisingly after I forced rebooted the VM, the system still loaded up properly. But I had to run dpkg --configure -a to finish configuring packages. Then use apt autoremove to clean up any unused packages. There was no broken packaging. So that’s promising.
Gonna maybe give it another week or two. Again, I am in no rush. Just gonna wait until the upgrading process is a little more smoother.
I want to ensure that my system won’t be out of commission. Because it’s my daily driver for essentially everything I do.
