UPDATE: Resolved, it was an issue caused by a faulty display port cable. Different issues from this cable had happened recently, I just initially assumed it was a software issue due to the fact that only GDM was affected.

It would work, but likely only as a temporary fix. Unless I intend to switch away from GNOME permanently, I’d be unable to lock my screen, since GNOME uses GDM specifically for screen locking.

Edited to include now

Will likely roll back in grub on the next boot. Thanks for reminding me I can do that

Logs, as in what shows up in journalctl? Also, when you suggest purging and reinstalling gdm, what issues are you saying I might run into?

I get that. Personally, as someone who worked on a Mac and had a Windows PC at home, it probably would’ve been easier to use KDE, since I did need to learn a bit of gnome’s ui, but I just found it so much cleaner compared to KDE. Might try heavily customizing KDE again sometime, I just couldn’t get the hang of it. At least for now, I can get a nicer desktop for me by using GNOME with minimal extensions than I can with KDE. I don’t like the Windows 10 adjacent style, but of course, to each their own. Not to say I find GNOME perfect, the complete lack of usability of custom themes as of gtk3 (Gradience has never actually worked for me) is infuriating, but ultimately I prefer my GNOME setup over what I’ve tried out in plasma.