KDE Neon 24.04 LTS completely broke my system đź’Ą

Help
1

I just installed the 24.04 LTS update and it completely broke my system. At boot, it just says “Reset system” for a splitsecond and then reboots endlessly. This is not the first time neon broke after an update. I am using the user edition, not the testing one, and never messed with the kernel or drivers! All I did is install some stuff from Discover, so why does this keep happening?

This is completely unacceptable for a supposedly stable distro. Dear KDE team, I love your desktop and Neon is great for checking out new features but its stability issues suck so much that I had to reinstall it multiple times already. It is not usable in daily life. Maybe you should rename user edition to testing and testing edition to experimental.

Luckily, kubuntu released their 24.10 update today which includes Plasma 6.1. Lets see if thats more stable

2

Not sure if I had the same problem as you but I think it is a broken “offline” update.

Happened for me on a fresh install… after my first reset after updating I also booted to a blank screen with no mouse, no desktop, could not ctl+alt+fx and open a new terminal session.

I had to reboot into safe mode, turn off the “offline” update and manually update then it worked. IDK why that option is on by default.

3

Lucky you. My system reboots even before reaching grub

4

The “User” edition is for enthusiast KDE users who expect a bit more polish. Please note that the focus of the “User” edition is still KDE software only. There is no thorough review of the complete software stack to guarantee a rock solid day-to-day experience.

5

Does holding “shift” bring up the boot options?

6

Thank you for changing the description :+1:
I remember it saying something like “Ideal for everyday use” a few months ago when I had to reinstall it. Now the description is much better.

Edit: Imo it would be very useful changing the name as well. There are countless of old linux guides out there recommending the user edition for everyday users. Changing the name to “Enthusiast edition” or something would further clarify who it is intended for, and prevent people who are blindly following an old guide from making a mistake.

1 Like
8

Unfortunately no. It crashes instantly after Post. I guess its backup recoverin’ time (again :roll_eyes:)

9

Did you check the boot order in your bios? The upgrade may have installed updated firmware, which can on occasion cause the boot order to reset.

10

Ug. Upgrading to 24.04 LTS broke mine too. There’s a bunch of dependancy problems.

1 Like
11

After reading this, I’m glad I am not in a rush. Still on 22.04.

For the future, you should all 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 :smile:

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.

12

Yeah… I only end up in Bios too. Seems the disk can’t boot anymore. :frowning:

13

Well in my case it started the upgrade process but it totally blocked the OS.

After around 20 min of it blocked i had to it the Reset button on the PC.

Neon booted up but it totally screwed the repos.

Is there any way to get the repos back (reset repos)???

14

Yeah… getting to terminal i also got this same thing!!! A lot of dependencies problems…

15

Didnt even think of that. Some other people wrote that the update messed up their boot entries. But I already installed a different distro anyway so whatevs

16

well if i can’t fix it and i have to reinstall i’m considering moving to fedora…

17

I tried a handful of things to no avail. I’m installing Kubuntu (although death to snaps. lol) I’ve tried a bunch of DE’s the past 6 months, and always landed back to KDE, and KDE Neon. Had various issues with all the others. But Kubuntu just released with 6.1, so I’m all over it.

18

The update also broke my system too, timeshift with btrfs rescued it

19

Got also black screen or graphics in rescue mode. And no exotic graphics card here - just plain intel…

Currently keeping back the update - 22.04 with Plasma6.2 is perfect here :wink:

20

Yeah dont install it until stuff gets fixed. But ignoring updates will be really annoying in the long run. If you dont want an arch-like user experience (aka having to fix stuff every few weeks), the only real solution is switching distros. Even Tumbleweed has been more stable the last few months, which is quite insane considering it is a rolling distro whereas neon is based on ubuntu

21

I had a similar experience with one of my computers while the other was fine. My main computer wouldn’t even get into grub. What I think happened is that the upgrade added a new efi boot entry for the upgraded system (KDE neon) but didn’t remove the old entry (neon) and my mobo didn’t bother updating which efi boot entry was getting used. What solved it for me was booting off usb, and deleting the old neon uefi boot entry with efibootmgr.

Before:

$ efibootmgr
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0000,0001,0002
Boot0000* neon      HD(1,GPT,d73f07b6-8379-6741-beac-d0afc7a0f61e,0x1000,0x96000)/File(\EFI\neon\SHIMX64.EFI)
Boot0002* KDE neon      HD(1,GPT,d73f07b6-8379-6741-beac-d0afc7a0f61e,0x1000,0x96000)/File(\EFI\KDE\SHIMX64.EFI)
Boot0006* UEFI: UFD USB Flash Drive 1100        PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(5,0)/USB(0,0)/CDROM(1,0x1d0,0x8b00)0000424f
Boot0007* UEFI: UFD USB Flash Drive 1100, Partition 2   PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(5,0)/USB(0,0)/HD(2,MBR,0x1bf6fa93,0x1d0,0x22c0)0000424f

See how Boot0000 says “neon” and Boot0002 says “KDE neon”. Using efibootmgr, you can delete the neon entry:

$ efibootmgr -B -b 0

After that, the boot entries look like:

$ efibootmgr
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002
Boot0002* KDE neon      HD(1,GPT,d73f07b6-8379-6741-beac-d0afc7a0f61e,0x1000,0x96000)/File(\EFI\KDE\SHIMX64.EFI)
Boot0006* UEFI: UFD USB Flash Drive 1100        PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(5,0)/USB(0,0)/CDROM(1,0x1d0,0x8b00)0000424f
Boot0007* UEFI: UFD USB Flash Drive 1100, Partition 2   PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(5,0)/USB(0,0)/HD(2,MBR,0x1bf6fa93,0x1d0,0x22c0)0000424f
1 Like