This isn't me asking for help or anything, I already replaced it with fedora kinoite. I just felt like talking about this ridiculous venture of mine.
So a couple weeks ago I started hyper focusing on cities skylines, but played on my Xbox. I learned that mods and all kinds of fun custom content was available on PC so I tried to play on my system. Problem, my laptop has an rtx 2070, but I was running fedora kinoite and couldn't figure out how in the world to install nvidia drivers.
So after a bunch of searching around I give up and decide to try installing a "gaming" focused distro in the form of endeavour os. It was awful.
Maybe I am weird but the x11 rendering didn't feel good at all, the lack of some default applications, as well as a bunch of apps I didn't know the purpose of. (This one is my own fault since they have a kde spin, but I remembered why I didn't like gnome) and finally today it froze in the middle of an update and hard rebooted, no longer able to launch.
Worst part, I didn't do a lick of gaming on the thing cause I moved on to Borderlands 3
I just updated gdm-prime on Manjaro to 46.0, when gnome shell is 45.6, and now gdm keeps crashing on startup.
gnome-shell is at 46.1. Also, gdm-prime is AUR so it's not supported.
This is one of those problems that Manjaro fans on Lemmy keep telling me are impossible.
I am on EndeavourOS and gnome-shell is on 46.1-2. gdm-prime is on 46.0-1. Everything would work fine using gdm-prime from the AUR.
The issue is that Manjaro holds back the packages in core and extra for weeks but the packages in the AUR are up-to-date ( and expect the version numbers found in Arch ). So you have this incompatibility.
You may find a newer version of gnome-shell in the AUR but, if you do, you may find that the Manjaro package never catches up and you are stuck with an AUR version forever, or worse, end up with packages that cannot be upgraded one the one in the AUR gets abandoned.
In my opinion, using Manjaro is “hard mode” much more than EndeavourOS is for exactly these kinds of reasons.
I fixed the problem by updating gnome-shell with the terminal