Hi guys! I have KDE Neon 6.2.3 running on my Surface Pro 7+, and up until now it’s been running rather smoothly, for years. But today I seem to be unable to fully boot anymore on normal mode. Linux will get stuck on the KDE spinning gear, with the gear frozen. And it becomes unresponsive, to open alternative consoles with control+alt+Fx, or even control+alt+del. The only thing that works is a force shutdown by holding the power button.
I tried with a previous kernel, with the same results (current is linux-image-6.10.10-surface-1, I have a generic 6.8.0-49, but it also freezes). I can boot in safe mode. It opens a different login screen, and after a failed attempt of opening lxde, it fails back to my usual KDE session, in safe graphics mode.
What can I test? How can I see what failed at boot?
You must log in or # to comment.
When you’ve booted in safe mode you can use journalctl to check what’s going on.
https://www.howtogeek.com/499623/how-to-use-journalctl-to-read-linux-system-logs/
https://www.man7.org/linux/man-pages/man1/journalctl.1.htmldeleted by creator
You can use the -b flag to get a specific boot sequence:
https://www.howtogeek.com/499623/how-to-use-journalctl-to-read-linux-system-logs/#reviewing-boot-messagesSometimes it can help to filter by UID 1000:
https://www.howtogeek.com/499623/how-to-use-journalctl-to-read-linux-system-logs/#selecting-log-messages-by-data-fieldsOther than that you can try to filter by KDE services, but as I run GNOME I’m not very familiar with their names. In the KDE forum a developer recommends using this for another problem:
journalctl --user-unit=plasma-plasmashell.service --boot 0 --no-pager
https://discuss.kde.org/t/black-screen-after-login-how-to-troubleshoot-plasma-desktop/1615/4deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
Oh, and before trying fixes - make a backup of your precious files when booted in safe mode.
deleted by creator
I think you’re gonna find that a hard task. There isn’t one universal directory where apps saves their configs and bin files. You’ll find some in ~/.config
deleted by creator
All I can see in that is that your machine has an LTE SIM slot and that the LTE Modem isn’t supported. That shouldn’t stop you from booting.
deleted by creator
If a clean install also fails then I would start considering hardware fault.
You could always check if you can boot Fedora Workstation with GNOME just in case but I think you should start looking for a replacement PC.deleted by creator
Sweet, then you know what’s going on and solved it!
You might wanna try out if your distro is compatible with cockpit:
https://cockpit-project.org/
https://github.com/cockpit-project/cockpitIt gives you a webUI that you can use to check out logs and services (among other things) and makes it a lot easier to troubleshoot computer troubles where the machine starts but your GUI doesn’t.
Did you update anything recently? Especially graphics drivers?
deleted by creator
deleted by creator
deleted by creator
Hi, I am a KDE Neon user too. While I never had this specific problem, I had various severe bugs appear randomly after system updates. Usually they get fixed again in future updates. So check regularly for system updates to see if this gets fixed.
Additionally try switching global theme for example from Breeze Dark to Breeze Light. Sometimes the global theme gets corrupted.
