Boot log/kernel/dmesg, X/Wayland/kde primarily. Been a long time since I’ve had to troubleshoot something like this so I don’t know the new kids on the block. Maybe upstart or dracut? Whatever manages the boot process now
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?
Yeah that might be it. Sddm is a display manager, you might be using it for your login screen.
You might be able to work around it by just setting the service to restart automatically, so that it comes up properly once a display is attached. But if you can, I would try reproducing it on a fresh and fully updated install, and open a bug report to the maintainers if you can. Linux developers generally try to make really sure their programs don’t crash like that.
I’ll check them tomorrow. Should I look for some specific messages? Or the general KDE init process?
Boot log/kernel/dmesg, X/Wayland/kde primarily. Been a long time since I’ve had to troubleshoot something like this so I don’t know the new kids on the block. Maybe upstart or dracut? Whatever manages the boot process now
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 -kto get the log from the current boot and piped it intogrepfor 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 readssddm-greeter-qt(1387): segfault ar 1b .... libLayerShellQtInterface.so.6.4.1...Guess that’s the issue?Yeah that might be it. Sddm is a display manager, you might be using it for your login screen.
You might be able to work around it by just setting the service to restart automatically, so that it comes up properly once a display is attached. But if you can, I would try reproducing it on a fresh and fully updated install, and open a bug report to the maintainers if you can. Linux developers generally try to make really sure their programs don’t crash like that.
Might as well try. I have a spare SSD lying around. Tnx for the assistance!