We use affiliate links to earn us some pennies. Learn more.

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.
12 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. You can also follow my personal adventures on Bluesky.
See more from me
You can also find comments for this article on social media: Mastodon
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
21 comments Subscribe
Page: 1/2»
  Go to:

scaine a day ago
  • Contributing Editor
  • Mega Supporter
For shame, Liam!!

I always assumed Simon was part of Canonical. Such a big community around all this, I'm kind of surprised something like this doesn't happen more often. Test, test and test again, I suppose.
R Daneel Olivaw a day ago
  • Supporter
Wow, that's pretty major! I would have just thought that a bug like that in beta would have been fixed for sure. I suppose not enough people reported it like you said or the reports were just overlooked. I know in my work, if one person reports something I ignore it, if a few people report something, I look into it, if a lot of people report something, EVERYONE looks into it. So in this case, it may just not have been enough reports to deem it worthy?
Ehvis a day ago
  • Supporter Plus
It did it to me today. Easy fix if you know what you're doing, but that's probably not everyone.
benstor214 23 hours ago
  • Supporter
Is this sddm not finding the config file? I had something similar a while ago.
Ehvis 23 hours ago
  • Supporter Plus
Is this sddm not finding the config file? I had something similar a while ago.

No. All KDE packages get uninstalled. Including the SDDM themes, so it has nothing to display.
M@GOid 21 hours ago
I learned from Windows to always do a fresh install. This is why I would never be affected by something like this.
PirateSkogen 21 hours ago
I upgraded my laptop from Ubuntu 24.10 to 25.04 yesterday and (fortunately) did not encounter this issue. My laptop doesn't appear to have pyqt6 installed on it. Maybe it was present during/before the upgrade? Definitely not something I would have checked on my own before upgrading.
tuxisagamer 21 hours ago
This was "fun" last night. I was running the upgrade in konsole which was uninstalled so it stopped responding, had to restart, boot an old kernel, resume the install, uninstall kdsoap-ws-discovery-client, then install kde.
sudoer 19 hours ago
That is not the first time in recent times, 13 hours ago in I wrote

Kubuntu has been in constant decline since at least 23.04, (basically it's been like that since the main maintainer left and did KDE Neon with more people leaving constantly I assume) I wouldn't recommend it. Just look at all the upgrade problems emerging with 25.04 and all the mispackaging issues and misconfigurations since 24.04. Personally I couldn't enable video hardware acceleration with Chromium only in 25.04 beta but I could basically everywhere else, OpenMandriva, Fedora, Elementary and what not. If you want KDE from the so-called "mainstream" distros, Fedora KDE edition is most probably the better and more professional choice.

https://www.gamingonlinux.com/2025/04/ubuntu-25-04-plucky-puffin-is-out-now/comment_id=277967


Last edited by sudoer on 19 Apr 2025 at 11:55 am UTC
Talon1024 18 hours ago
  • Supporter Plus
The last time I tried upgrading my Kubuntu 22.04 to 24.04 using the official release upgrade tool, I was left without a Linux kernel. Then again, I have my root and home folders on separate partitions, and the root partition was rather small (200GB) and I had a lot of system packages installed, so it may have been a disk space issue... I really have no idea. I had to install Kubuntu 24.04 from the DVD, and I had to format my root partition in the process, but at least I didn't lose any of the stuff in my home folder!


Last edited by Talon1024 on 19 Apr 2025 at 12:32 am UTC
Eike 12 hours ago
  • Supporter Plus
I learned from Windows to always do a fresh install. This is why I would never be affected by something like this.

I didn't apply what I learned from Windows bugs to Linux and I'm happyly upgrading my Debian installation most of the times for 25 years.
Fear thou not.


Last edited by Eike on 19 Apr 2025 at 9:19 am UTC
tannertech 10 hours ago
  • New User
I was about to upgrade my Kubuntu install yesterday and then realized better off waiting. Always pays off lmao
Antonio Storcke 10 hours ago
  • New User
To say it politely, KDE is not ready for prime time. It is feature-bloated and full of half-baked features. Ubuntu is learning their lesson now. Fedora will learn their lesson later. Cosmic has done in mere months what KDE has tried and failed for 30 years to do.
Liam Dawe 10 hours ago
  • Admin
That’s a really odd thing to say. KDE Plasma has been ready for a long time, while COSMIC is Alpha with lots missing. I use Plasma every day and am very happy with it.
Mrokii 8 hours ago
@Antonio Storcke

To say it politely, KDE is not ready for prime time. It is feature-bloated and full of half-baked features. Ubuntu is learning their lesson now. Fedora will learn their lesson later. Cosmic has done in mere months what KDE has tried and failed for 30 years to do.

To say it not so politely: Stop spreading bullshit. There are numerous people who like the feature-rich Plasma-desktop (including me), and most of its features are decidedly *not* half-baked. The transition to Plasma 6 was exceptionally smooth, in my experience. The general OS-Upgrades every half year have been rock-solid for me for many years now. Bugs like these are unfortunate, but Plasma isn't the first nor the last to experience something like that on occasion.

And please stop comparing companies with a clear vision (and no need to wait for decisions by numerous people, plus the ability to *pay* their employees to do work) with a community of mostly volunteers that usually don't get paid for their hard work. Doing so is either disingenuous or it shows that you have no clue what you're talking about.

Having said that, I did experience the bug, and for those who struggle with it: Just switch to a TTY and reinstall the plasma-desktop, but using apt, that problem was solved in a few minutes. After that, one can reboot, enter their password and go on installing the rest of the default apps via the GUI.

It's far from a catastrophe, as the system is still booting, just with Plasma removed.
sudoer 7 hours ago
To say it politely, KDE is not ready for prime time. It is feature-bloated and full of half-baked features. Ubuntu is learning their lesson now. Fedora will learn their lesson later. Cosmic has done in mere months what KDE has tried and failed for 30 years to do.

I mean sometimes I feel like trolling a bit too, but you 've gone full *******


Last edited by sudoer on 19 Apr 2025 at 12:00 pm UTC
iwantlinuxgames 4 hours ago
I had to boot from a Live USB and do a chroot into the root of my install. lost network connectivity upon finishing the upgrade. so, for any adventurous early adopters:

boot from a live USB. once at a desktop open a Konsole terminal.

mkdir target
sudo su
mount -o bind /dev target/dev
mount -o bind /proc target/proc
mount -o bind /sys target/sys
cp /etc/resolv.conf target/etc/
chroot target

once you're in the chroot at the propmpt you can run

sudo apt install plasma-desktop

let it do it's thing and reboot.
Caldathras 4 hours ago
Oof! I'm with @M@GOid and @tannertech on this one. I typically wait a couple minor updates before taking on the next major update. Gives the devs a chance to work out the kinks and is less hassle for me.

I guess I should say thanks to early adopters, though, as they are the ones who identify those kinks.

------
That being said, I was testing Kubuntu's major upgrade feature in a VM a while back. After the second upgrade, I could only login to KDE in Wayland mode. Xorg would cause Plasma to lock up and crash. So, not the first time the upgrade tool buggered things up ...


Last edited by Caldathras on 19 Apr 2025 at 3:24 pm UTC
mr-victory 3 hours ago
@iwantlinuxgames I know this sounds very wrong but you can use arch-chroot to automate the chroot steps. Basically `sudo apt install arch-install-scripts` then `sudo arch-chroot /mnt/`, no need to mount /dev etc.
tmtvl 3 hours ago
Beta users shouldn't feel responsible, if a thing requires pyqt6 (or anything else) and the system doesn't have that component installed by default and the package declaration doesn't include a 'requires pyqt6' statement; then the build system should error and the package shouldn't build. That's what RPM buildroots are for (and it's why the Arch wiki recommends building in a clean chroot).
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register