Ubuntu 25.04 upgrades halted due to Kubuntu users getting a broken desktop

This is a bit of a major woopsie. The upgrade path for the latest Ubuntu 25.04 release has been pulled offline, as it has resulted in Kubuntu users seeing a broken desktop.

What you end up with is a weird looking login screen, and nothing seems to work.

Picture credit: @dimspace.xyz on Bluesky

I actually encountered this bug during the Beta, thinking I had done something wrong or not paid enough attention. Turns out, it was a real genuine major bug. I probably should have reported it, but I’m always doing multiple things at the same time and quite overworked right now. So, uh, feel free to blame me I guess? Developers can’t fix stuff they don’t know about — woops.

Writing on Reddit in replies to posts about the problem, Simon Quigley the Lubuntu Release Manager, wrote:

Here’s what’s going on with this, because yeah, there’s something going on.

It’s my fault personally, sorry folks.

So, when you go to upgrade from Kubuntu 24.10 to 25.04, the actual installer is grabbed as a tarball from the archive.

In other words, Kubuntu 25.04’s upgrader is used to upgrade to 25.04, from 24.10.

Well, I ported it to PyQt6 this cycle. A few weeks before release, I was pinged with someone notifying me that Kubuntu, Ubuntu Studio, and Lubuntu didn’t actually come with pyqt6 installed.

Literally, installing pyqt6 should fix your issue, for now. If you run into actual issues with the Kubuntu install after upgrade, I’m much more concerned.

We have a fix, in the queue. Waiting. Sitting. We had the release today. I’m surprised people are able to upgrade already, and if someone already enabled the upgrades without checking with me… I’m going to be unhappy, to say the least.

Some cross training is happening, we’re working it out. For now, this was me, sorry about that folks.

And then in a follow-up post:

Hi folks, just a quick update on the latest.

Yes, 25.04 upgrades are broken beyond just adding pyqt6 as a dependency. While I had something to do with it, there’s a much greater issue at play that we don’t know about yet.

From everything I can possibly read, enabling upgrades this early was a genuine mistake not found in code review. I have done everything in my power to slam the brakes on the upgrades, not just for Kubuntu, but for everyone. All ten flavors, plus Desktop, and Server.

Yes, I personally pushed the code change disabling those upgrades. It required one more manual step, and now it’s deployed.

As of about 20 minutes ago, I’ve passed off to the official Ubuntu Release Team who will now drive this to completion. The change I made was to mark Plucky as unsupported temporarily, which will halt the upgrades, with a POSSIBLE side effect of an end of life popup, on your Plucky machine.

Ignore the popup, it was just the quickest solution to throw a wrench in the gears.

I’m genuinely sorry about this. On behalf of Ubuntu, on behalf of Kubuntu, and on behalf of my own flavor, Lubuntu. This is unacceptable, and I will be persistent in making sure our processes become better.

I’m going to try to go to sleep now. This thread is what alerted me that there’s a wider issue, specifically. So, thank you all.

We’ll be better. If you need help picking up the pieces, yes, we have support channels for basically everything. The best thing is to just make sure the kubuntu-desktop package is already installed.

I hope you can also understand my position. I have never worked for Canonical, I work for Altispeed Technologies. Please go support the Ask Noah Show, Noah is the one who made sure I had enough coffee to survive this thing.

Accidents and bugs happen, hopefully some lessons will be learned from all sides on this. Just goes to show, Beta releases are vital to pick up bugs…if they’re reported.

Article taken from GamingOnLinux.com.