Linux

8622 readers

140 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.

founded 2 years ago

MODERATORS

MigratingtoLemmy

Help to troubleshoot...Freeze before desktop (lemm.ee)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/linux

21 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[–] anamethatisnt 4 points 2 months ago (16 children)

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.html

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago) (15 children)

Thanks. I pulled the journalctl. This is...A bit extensive. EDIT: Well seems I only can see the KDE logo and a frozen gear, but according to systemctl the system is up and running, and the network connected? After 7 seconds frozen I give up once more and hold power button, since this is the only thing it seems to react to, and yet, even this gets logged onto journalctl.

[–] anamethatisnt 3 points 2 months ago

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-messages

Sometimes 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-fields

Other 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/4

load more comments (14 replies)