Hello everyone!
I was very happy to use KDE Neon 22.04 - it was a fantastic experience and great stability for a month.
When I saw the news that the distribution was updated to 24.04.1, I decided not to update via the system update utility, but to install the OS from scratch, downloading the image “neon-user-20241010”. The installation went fine, after the first launch I installed some applications. Everything worked fine. But the next day, when I selected KDE Neon in the GRUB menu, the system refused to boot - a black screen, then the screen goes out, then some sound noise and then instead of the login screen, a black screen. At the same time, the system responds only to Ctrl + Alt + Del, during which the disk access indicator on the system unit blinks.
Several reboots in a row, the situation repeated. I was upset, but the next day the system booted without any problems!
And at the moment, the situation is repeating itself - sometimes the system does not boot, and sometimes it boots without problems.
What could be the problem and why has this never happened on 22.04?
I had the same intermittent issue. There are a few other threads about the problem, here or for kubuntu, and the recommended workaround is to go into /etc/default/grub and remove the splash and quiet from GRUB_CMDLINE_LINUX_DEFAULT (or possibly add nomodeset though it seems unnecessary for most people), then run sudo update-grub to apply the changes. If you’re having trouble booting long enough to make that change, you can hit escape at boot to bring up the grub menu and adjust the options before boot (or just select an older kernel to boot from, that seemed to shake things up enough to temporarily fix it for me, but that may have just been a coincidence).
It’s only been a day since I made those changes. No issues so far, but maybe it’s too soon to know for sure if that fixed it.
1 Like
Thanks for the reply!
Since my message, there have been several system updates and the problem has stopped appearing. I will continue to observe. Of course, I would like the problem to be fixed by the distro itself, and not by manual fixes.
If the problem appears again, I will use the instructions above.
By the way, I have constantly encountered this problem with loading the system over many Ubuntu releases (on VirtualBox), but at the same time, Mint has always been guaranteed to load.