Try enablingKMS Early Start. This fixed it for me
2 Likes
Recommenting the WaylandEnable=false line in /etc/gdm/custom.conf worked for me. For some reason it was uncommented by default.
After a while without using my Manjaro installation, I got a huge update and also Wayland stopped working in Gnome: only two options available to login (Gnome and Gnome Classic, no Gnome on Xorg) and it would always run on Xorg.
I have checked custom.conf, tried KMS Early Start, nothing worked. Then I found this post in the Arch forum:
bbs.archlinux.org/viewtopic.php?id=258520
and it worked. I also changed StandardOutput to journal in the original gdm.service module to fix some startup error messages.
Cheers
2 Likes
For me, the problem was nvidia. Gnome disables wayland when it detects nvidia. I just had to disable it in some rules config.
To let GDM use Wayland, copy
61-gdm.rulesfrom/usr/lib/udev/rules.d/to/etc/udev/rules.d/(where the latter file will override the former) and comment out the related line:
# DRIVER=="nvidia", RUN+="/usr/lib/gdm-disable-wayland"
source: arch wiki on GDM. (I can’t include the link in here. Idk why.)
There’s no need to bump old threads when there is already a known workaround for the issue on topic.