Wayland does not play well with proprietary drivers. Currently the biggest issue is that NVIDIA does currently not support Xwayland properly, so apps that require it get software rendering. This includes most games, which are the most common use case for proprietary NVIDIA drivers. This is why GNOME automatically disables Wayland if you have NVIDIA.
However, if this does not deter you, you can use Wayland with NVIDIA drivers. Here is how to do it:
Edit the /etc/gdm/custom.conf file and comment out the line WaylandEnable=false. The correct file will then look something like this:
# GDM configuration storage
# Uncomment the line below to force the login screen to use Xorg
# Uncomment the line below to turn on debugging
To force-enable Wayland, disable the udev rule responsible for disabling Wayland in GDM:
Since updating to the Nvidia 495.44 drivers (now in Stable) one thing I noticed is that the contents of 61-gdm.rules in that howto are pretty different to how that file looks now. It looks like there is now logic in there to detect the nvidia driver version number and only disable wayland if the version is lower than 470. However on my system with 495, Wayland does not seem to be an option on the GDM sessions list. So at the very least the instructions here might need to be updated. (and i can’t comment directly in that thread because it got locked)
Yep, noticed that, too. I haven’t gotten around to updating the tutorial. In theory my system meets the criteria to use Wayland by default, but logs show some condition wasn’t met, but doesn’t say what.
So after the stable update, I noticed I was back on X11. Came back to this post, checked all the settings and also noticed the gdm.rules had changed a lot as @JPL mentioned.
Implemented the above fix and am now back on Wayland but it kind of feels strange. With all the Wayland progress and with the fixes 495 driver brings, shouldn’t Wayland just work without a hacky “comment these lines” fix?
I had exactly the same experience and I also enabled wayland the same way, but I guess something is missing.
I’ve been reading about how nvidia’s 495 drivers will natively support wayland via GBM instead of EGL streams, but I am not sure this is enabled, as I see the same problems in wayland as before, including some enough rendering problems to not make it ready for use yet IMO.
I’m not sure if a gdm package update or something else fixed it, but my system version of 61-gdm.rules with no modifications now properly shows the Wayland option on the login screen. If this is true for other nvidia users as well, that means one less step to enable wayland.
It doesn’t for me, sadly. Also, when I did follow the instructions to use Wayland, Firefox wouldn’t start unless I started in safe mode, and starting it with MOZ_ENABLE_WAYLAND=1 made it start but it crashed and refused to start even with the option when I tried to check “about:support” to make sure it was running on Wayland, heh. Other applications didn’t render properly (Element, a chat client, showed a blank window with just the application background colour) and some GNOME extensions seemed to break, like “Blur my shell”.
After the latest stable update, I rebooted to X11 again.
When I just went through all the steps in the initial post again, all the changes I made in the past seemed to still be there. So I think one of these must have been the reason why it switched back to Wayland after a reboot: