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
this post was submitted on 03 Dec 2024
22 points (92.3% liked)
Linux
8233 readers
135 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
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.
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
You need to specify the -b switch or you're just looking at logs for the current session. Something like journalctl -xe -b 1 should do the trick.
Just an update. Today I made a rescuezilla full backup of the whole drive, and then wiped and installed KDE Neon brand new from Dec 1st release from their page. Guess what...that one ALSO fails to boot.
OK so just to confirm: you get a boot freeze even on a fresh install before you restore a backup?
Are you able to boot a liveusb?
I would try another distro just to rule out a software problem but it sounds like hardware failure. I would test your ram, graphics card, and storage medium. Do you have an SSD or an HDD?
Oh, and before trying fixes - make a backup of your precious files when booted in safe mode.
About that - I´d like to run a backup that takes all apps and their configuration files (more than my own docs and files, which I already have properly backed in Seafile). What would you recommend just for the apps, their configs (and maybe the repos) etc?
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
Dec 03 16:27:12 SurfaceNeon wpa_supplicant[1436]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=HK
Dec 03 16:27:12 SurfaceNeon NetworkManager[1428]: <info> [1733214432.6906] manager: startup complete
Dec 03 16:27:12 SurfaceNeon systemd[1]: Finished NetworkManager-wait-online.service - Network Manager Wait Online.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Reached target network-online.target - Network is Online.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Started update-notifier-download.timer - Download data for packages that failed at
package install time.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Started update-notifier-motd.timer - Check to see whether there is a new version of Ubuntu available.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Reached target timers.target - Timer Units.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Started cups-browsed.service - Make remote CUPS printers available locally.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Started deluged.service - Deluge Bittorrent Client Daemon.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Reached target multi-user.target - Multi-User System.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Reached target graphical.target - Graphical Interface.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
Dec 03 16:27:12 SurfaceNeon systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
Dec 03 16:27:12 SurfaceNeon systemd[1]: Startup finished in 4.484s (firmware) + 6.837s (loader) + 3.208s (kernel) + 11.614s (userspace) = 26.145s.
Dec 03 16:27:12 SurfaceNeon systemd[1]: dmesg.service: Deactivated successfully.
Dec 03 16:27:14 SurfaceNeon ModemManager[1454]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin
Dec 03 16:27:20 SurfaceNeon systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 03 16:27:20 SurfaceNeon systemd-logind[1351]: Power key pressed short.
Dec 03 16:27:20 SurfaceNeon systemd-logind[1351]: Powering off...
Dec 03 16:27:20 SurfaceNeon systemd-logind[1351]: System is powering down.
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.
Yeah...It looks to me like it just says it went alright, right until I hit the poweroff button, because it's actually completely crashed.
Just an update. Today I made a rescuezilla full backup of the whole drive, and then wiped and installed KDE Neon brand new from Dec 1st release from their page. Guess what...that one ALSO fails to boot.
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.
Did you update anything recently? Especially graphics drivers?
Just an update. Today I made a rescuezilla full backup of the whole drive, and then wiped and installed KDE Neon brand new from Dec 1st release from their page. Guess what...that one ALSO fails to boot.
I mean...I run the software discover update almost daily, whenever the icon pops in the tray...I don't remember seeing anything scary on the update list, but I might have missed it.
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.