EndeavourOS boots into console login, not KDE

[CertifiedHuman]

For some reason, whenever booting from Grub, I’m presented with a console only login screen. I can log into it, but I don’t know how to actually get out of it and into the desktop environment (KDE).

Also sorry if I’m not providing enough information, this is my first time posting and I’m very nervous about the situation.

[dalto]

Did you uninstall some packages recently?

Either way, your only option is to login to the console and see what it going in.

[Bink]

Welcome @CertifiedHuman!

You might see if you can start KDE, once logged in.

• To start a Plasma on Wayland session from a console, run

/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland

• To start Plasma with xinit/startx, append export DESKTOP_SESSION=plasma and exec startplasma-x11 to your .xinitrc file or run directly in the console startx /usr/bin/startplasma-x11. If you want to start Xorg at login, please see Start X at login.

From:
https://wiki.archlinux.org/title/KDE#From_the_console

Of those, the easiest to quickly test may be:

startx /usr/bin/startplasma-x11

[CertifiedHuman]

It actually works thanks. But one thing, how could I have it go to the GUI by default?

[Bink]

SDDM is the default display manager for handling that. For some reason on your setup, it’s not starting. You might review the SDDM Wiki page and compare the recommended configuration to your own, to see what might be amiss.

https://wiki.archlinux.org/title/SDDM

You might also look here at “Loading the display manager” :
https://wiki.archlinux.org/title/Display_manager#Loading_the_display_manager

[CertifiedHuman]

Alright, initally I was just using startx /usr/bin/startplasma-x11 as @Bink suggested, but eventually after months of it, I was starting to really miss it actually going automatically straight to the GUI as it used to before. So this was the command that helped with that:

systemctl set-default graphical.target

Since before I used the command, it turns out the default target to boot into was multi-user.target, which apparently wasn’t the right one.

I guess it just took a handful of months to actually force myself to fix it, but yeah it’s now fixed so that’s good.