I did all of that (ticked “Enable GDM Wayland” in GA), hit Apply, rebooted. When I get to the GDM login screen and click my name to log in, no gear shows up in the lower right-hand corner. I’m running the Garuda Gnome edition.
In the /etc/gdm/custom.conf, the Wayland=false setting is commented out.
Are there any other packages I need to install? This worked for me in the Dragonized KDE where I had apparently had to just install the wayland plasma package. Not sure about the Gnome image after a fresh install?
Yup. Already tried that. Didn't fix it. Still no cog-wheel like I've seen in Nobara Gnome and also when I was running the Dragonized version of Garuda. I just prefer Gnome because KDE seems very flaky for me.
it's saying Xorg with Xwayland. But I know with Wayland, I don't get screen tearing with games. I'm still seeing that right now, so I assume I'm still on Xorg.
The XDG_SESSION_TYPE value is x11 as well instead of wayland. Under KDE Dragonized and Nobara, I can fully switch to Wayland and XDG_SESSION_TYPE would say Wayland.
I've moved your issue to a new topic so it has better visibility. Please post the output of garuda-inxi, as well as the output of journalctl -b -u gdm.service.
Feb 11 08:43:19 blaviken systemd[1]: Starting GNOME Display Manager...
Feb 11 08:43:19 blaviken systemd[1]: Started GNOME Display Manager.
Feb 11 08:43:47 blaviken gdm-password][2512]: pam_systemd_home(gdm-password:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 11 08:43:51 blaviken gdm-password][2512]: gkr-pam: unable to locate daemon control file
Feb 11 08:43:51 blaviken gdm-password][2512]: gkr-pam: stashed password to try later in open session
Feb 11 08:43:51 blaviken gdm-password][2512]: pam_unix(gdm-password:session): session opened for user bolski(uid=1000) by (uid=0)
Feb 11 08:43:51 blaviken gdm-password][2512]: gkr-pam: unlocked login keyring
Feb 11 08:44:00 blaviken gdm[824]: Gdm: Child process -909 was already dead.
Feb 11 09:00:45 blaviken gdm-password][60688]: pam_systemd_home(gdm-password:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 11 09:02:44 blaviken systemd[1]: Stopping GNOME Display Manager...
Feb 11 09:02:44 blaviken gdm[824]: Gdm: Child process -59921 was already dead.
Feb 11 09:02:44 blaviken systemd[1]: gdm.service: Deactivated successfully.
Feb 11 09:02:44 blaviken systemd[1]: Stopped GNOME Display Manager.
Feb 11 09:02:48 blaviken systemd[1]: Starting GNOME Display Manager...
Feb 11 09:02:48 blaviken systemd[1]: Started GNOME Display Manager.
Feb 11 09:02:53 blaviken gdm-password][70305]: pam_systemd_home(gdm-password:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 11 09:03:16 blaviken gdm-password][71867]: pam_systemd_home(gdm-password:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 11 09:03:18 blaviken gdm-password][71867]: gkr-pam: unable to locate daemon control file
Feb 11 09:03:18 blaviken gdm-password][71867]: gkr-pam: stashed password to try later in open session
Feb 11 09:03:18 blaviken gdm-password][71867]: pam_unix(gdm-password:session): session opened for user bolski(uid=1000) by (uid=0)
Feb 11 09:03:18 blaviken gdm-password][71867]: gkr-pam: unlocked login keyring
Feb 11 09:03:22 blaviken gdm[70016]: Gdm: Child process -70023 was already dead.
Feb 11 09:20:40 blaviken gdm[70016]: Gdm: Child process -130388 was already dead.
Feb 11 09:38:22 blaviken gdm-password][183368]: pam_systemd_home(gdm-password:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 11 09:38:25 blaviken gdm-password][183368]: gkr-pam: unable to locate daemon control file
Feb 11 09:38:25 blaviken gdm-password][183368]: gkr-pam: stashed password to try later in open session
Feb 11 09:38:25 blaviken gdm-password][183368]: pam_unix(gdm-password:session): session opened for user bolski(uid=1000) by (uid=0)
Feb 11 09:38:25 blaviken gdm-password][183368]: gkr-pam: unlocked login keyring
Feb 11 09:38:30 blaviken gdm[70016]: Gdm: Child process -182616 was already dead.
Feb 11 09:39:14 blaviken systemd[1]: Stopping GNOME Display Manager...
Feb 11 09:39:14 blaviken gdm[70016]: GLib: Source ID 159 was not found when attempting to remove it
Feb 11 09:39:14 blaviken gdm[70016]: Gdm: Child process -185621 was already dead.
Feb 11 09:39:14 blaviken systemd[1]: gdm.service: Deactivated successfully.
Feb 11 09:39:14 blaviken systemd[1]: Stopped GNOME Display Manager.
Feb 11 09:39:17 blaviken systemd[1]: Starting GNOME Display Manager...
Feb 11 09:39:17 blaviken systemd[1]: Started GNOME Display Manager.
Feb 11 09:39:23 blaviken gdm-password][189780]: pam_systemd_home(gdm-password:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 11 09:39:25 blaviken gdm-password][189780]: gkr-pam: unable to locate daemon control file
Feb 11 09:39:25 blaviken gdm-password][189780]: gkr-pam: stashed password to try later in open session
Feb 11 09:39:25 blaviken gdm-password][189780]: pam_unix(gdm-password:session): session opened for user bolski(uid=1000) by (uid=0)
Feb 11 09:39:25 blaviken gdm-password][189780]: gkr-pam: unlocked login keyring
Feb 11 09:39:29 blaviken gdm[189506]: Gdm: Child process -189513 was already dead.
Thanks for the tips, but I have already tried everything it said in there and unfortunately, it's still not working.
I know in Nobara, it defaults to Nobara with Gnome in the official version. I also got it working under Garuda in the Dragonized KDE version so I know it works. I just can't see to get it to work with the Garuda Gnome image. KDE image had some weird issues for me. Gnome is just more stable for me.
I'm just wondering if there are some other packages I need to install? Again, I'm using the Garuda Gnome image.
Logging out I've already tried. The COG wheel never shows up like it has in other distros.
I've even CTRL-ALT-F2 to a tty, logged in and stopped and restarted gdm and that doesn't work either.
I've never had this issue with the Garuda KDE Dragonized version nor Nobara. Just for some reason the Garuda Gnome image. So I'm wondering if it's something is missing that I need to install? Does Garuda Gnome come with all the correct packages installed to switch to Wayland?
Yes, it is actually the default for Gnome and extra configuration is needed to get the “Gnome on Xorg” session type. My understanding is not much else should be needed except commenting out the Wayland=false line in /etc/gdm/custom.conf.
What happens if you run XDG_SESSION_TYPE=wayland dbus-run-session gnome-session from the TTY before logging in?
Yup, that causes my session to use Wayland. I guess that's a work around. Now I would like to make it so when I'm at the gdm login, I can click on the gear icon in the lower right-hand corner to choose between X11 and Wayland.
It links to a page in the wiki here which describes how to set up the NVreg_PreserveVideoMemoryAllocations=1 option, and a couple power management services that need to be enabled (nvidia-suspend.service and nvidia-hibernate.service). I will admit it is not entirely clear to me why this is related to logging in with Wayland, but from the sounds of it getting that set up may be all you need to do.
If that doesn’t do the trick, there is a note about overriding a udev rule that GDM sets up:
As of GDM 42 and NVIDIA driver 510, GDM defaults to Wayland. For older NVIDIA drivers (in between version 470 and 510), GDM has chipset-dependent udev rules to use Xorg rather than Wayland. To force-enable Wayland, override these rules by creating the following symlink:
# ln -s /dev/null /etc/udev/rules.d/61-gdm.rules
Note: This command works because rules in /etc/udev/rules.d/ override those in /usr/lib/udev/rules.d/ (see udev#About udev rules). It is also advised to modify files in /etc/ rather than in /usr/ as those are managed by pacman.
If, instead of GDM, a black screen appears, try disabling integrated graphics in your computer’s BIOS settings.
I saw that as well and tried it and it didn't appear to work. Since my drivers are the latest nVidia drivers (version 525.89.02) didn't create the link. I'll try again later to see if that works.
I download the Garuda Gnome image on 2/9/2023 as an FYI.
At this point, I've switched the KDE Dragonized version. I once got Wayland to work before under Dragonized, so if I have the need to try again, I'll do it there.
But at least with Xorg now, I have been able to keep my multi-monitor setup enabled without having to turn off all but one monitor to reduce screen tearing when playing games. So at this point, Wayland is not a priority for me.
Mod note: split from another topic here: Unable to switch to Wayland on GNOME