Wayland session no longer works after upgrading to Fedora 41

Hi guys,

I recently upgraded to Fedora 41 on my desktop. I have an NVIDIA Card in my system, and when I attempt to login into a wayland session (GNOME), I am booted back to the login screen. However, when I attempt to log into an X11 session, I am able to login without issue.

I tried uninstalling and reinstalling my drivers, and realized that my wayland session doesn’t work, regardless if I have NVIDIA drivers installed or not.

Another thing to note (somewhat off topic) is that I also have a Framework 13 laptop with an AMD Ryzen 7 7840U CPU, and I also upgraded that to Fedora 41 along side my desktop with the NVIDIA GPU, and the wayland sessions work without any issues on my Framework 13.

Any ideas on what I could try?
Any help will be greatly appreciated.

1 Like

There are reports that some systems fail to properly work with wayland on nvidia GPUs.

The general fix seems to be to edit the file /etc/environment and add DRI_PRIME=1 into that file.
Log out and back in then wayland should work.

unfortunately, that didn’t seem to work.

I tried rebooting, as well as logging out and still kicks me back to the login screen when trying to log into a wayland session.

I would like to add that the splash screen for the inital bootup also doesn’t show, showing background terminal processes instead. Not sure if this would help, but worth mentioning.

Just to double-check, are those Nvidia drivers installed via the instructions at Howto/NVIDIA - RPM Fusion ?

I had to use a method that had me assign a key for the nvidia driver to work, since my system uses secure boot, kinda like this:

FYI, I don’t know if this would relate to the specific issue you’re seeing, but there are steps to get Nvidia drivers working with Secure Boot enabled that are far, far less manually involved than what’s listed on that page:

https://rpmfusion.org/Howto/Secure%20Boot

If there are any issues there, I’ve used steps shared by Jeff V many times to fix Nvidia woes:

That’s actually how I imported my keys for secure boot to be used for my NVIDIA drivers. Was just trying to find the method from the top of my head. Never knew they had that on their website. My bad!

In case you haven’t fixed your issue yet, maybe setting the GSK_RENDERER env. variable to gl (instead of the new default vulkan renderer) might be a fix for you too (reboot needed)?

echo export GSK_RENDERER=gl | sudo tee /etc/profile.d/gtk_renderer.sh > /dev/null

Wanted to add my experience here as well. I have the same issue happening but it’s on my Framework 13 AMD Ryzen™ 5 7640U. When trying to sign in using Wayland, it just goes right back to the log in screen.

That didn’t work, unfortunately.

I also noted that wayland doesn’t work, regardless if NVIDIA drivers are installed or not.

Does it work with X11?

For my 3 options when logging in, GNOME xorg works just fine, GNOME Classic and GNOME (Wayland) both have the issue of jumping right back to the login screen with no other information as far as I can see.

1 Like

Interesting. As mentioned, I myself, also have a Framework 13, but I have a Ryzen 7 7840U. I wonder if it may have something to do with the upgrade process or something.

That is a rubbish guide which is written by a clueless person, you need to sign all the nvidia modules, not just nvidia.ko which for the record doesn’t exist!

$ rpm -ql kmod-nvidia-6.11.5-300.fc41.x86_64-565.57.01-1.fc41.x86_64
/lib/modules/6.11.5-300.fc41.x86_64/extra
/lib/modules/6.11.5-300.fc41.x86_64/extra/nvidia
/lib/modules/6.11.5-300.fc41.x86_64/extra/nvidia/nvidia-drm.ko.xz
/lib/modules/6.11.5-300.fc41.x86_64/extra/nvidia/nvidia-modeset.ko.xz
/lib/modules/6.11.5-300.fc41.x86_64/extra/nvidia/nvidia-peermem.ko.xz
/lib/modules/6.11.5-300.fc41.x86_64/extra/nvidia/nvidia-uvm.ko.xz
/lib/modules/6.11.5-300.fc41.x86_64/extra/nvidia/nvidia.ko.xz

Note there are no *.ko files

this gguide is not valid rpm-fusion has all what need to do including secure boot parts and is automated

I realized that. I didn’t actually do it that way.

I did it this way. Sorry for any confusion.

https://rpmfusion.org/Howto/Secure%20Boot

Some have reported that wayland works properly by adding GSK_RENDERER=ngl to the /etc/environment file then either logout and back in or reboot. Some have used the value gl or vulkan in place of ngl with success.

I tried setting the GSK_RENDERER to either gl or vulkan, and sadly, neither of them seem to work; it still kicks me back to the login screen when trying to login a wayland session.

What about ngl?

ngl doesn’t work either