No probs! I checked all the F-keys and non have the session initialized. The logs say that SDDM segfaulted. That's the last message. I typed it out in the commend above if you want to take a look.
Seems like you were right. I checked my logs with the monitor turned off and the last logged message is SDDM segfaulting.
I checked the logs and can't find anything interesting. I am not that knowlagable so you'll have to forgive me. I used journalctl -b -k
to get the log from the current boot and piped it into grep
for searching. There is no mention of kde, x11, xorg or wayland.
Ok, editing this while typing. SDDM is segfaulting. I have no idea what that is, but another comment mentioned it. The message reads sddm-greeter-qt(1387): segfault ar 1b .... libLayerShellQtInterface.so.6.4.1...
Guess that's the issue?
Ehm, what? I am pretty sure you are in the wrong post.
Here's a fun one. In Serbian an old name is "Godfather's straw" (straw as in the dry stalks of plants).
I'll check them tomorrow. Should I look for some specific messages? Or the general KDE init process?
I should have provided more details about my setup, but I was kinda hoping that it turns out to be trivial. I am on a desktop PC, AMD gpu, Mesa drivers, one 1440p monitor. Nothing special about the setup. I'll have a look at the URL you provided and try a few things tomorrow.
F1 is just a blank conosle with a blinking curses and you can't type anything into it. F2/3/4 open a new terminal from where I can log in, but none seem to have a KDE session running. Gotta check out the other F keys. Just in case none of the work, is there a solution you know of?
This is pure, unfiltered brain rot.
There's even a tooth emoji and somehow we all missed it
Some stupid meme about a girl who told in a street interview that men like to get sloppy blowjobs
Might as well try. I have a spare SSD lying around. Tnx for the assistance!