At the Grub menu, hit the E key and append space 3 to the end of the linu line before proceeding with boot. Do you get a shell prompt on any vtty after doing so? If yes, logs of current boot can be checked. If not, instead of 3, append nomodeset before proceeding. If the systemd journal is persistent, evidenced by existence of /var/log/journal/, run first sudo journalctl -b -1 -p3 (-1 gets journal of prior boot), and if it looks bad, share it here, as well as pastebinning sudo journalctl -b -1 so we can examine your prior "normal" boot's journal looking for more details of any bad graphics stuff. If /var/log/journal/ does not exist, create it, then start troubleshooting over with a normal boot attempt, and follow up accordingly per above.
If you have auto login enabled, disable it and try a normal boot. If a normal login screen appears, try an X11 session instead of Wayland, or a session type other than Plasma. If you are able to start an X11 Plasma or other DE or WM session, there should be a resulting file /var/log/Xorg.0.log.old from a previous boot you can scan for bad stuff, and another but without .old for the current boot.
If you have auto login enabled, disable it and try a normal boot. If a normal login screen appears, try an X11 session instead of Wayland, or a session type other than Plasma. If you are able to start an X11 Plasma or other DE or WM session, there should be a resulting file /var/log/Xorg.0.log.old from a previous boot you can scan for bad stuff, and another but without .old for the current boot.
Statistics: Posted by mrmazda — 2026-01-03 05:14