F39 wayland: Using the same machine Gnome freezes on the new install, but not on the old one

Hello there!

I’m having a very weird behavior:
I installed a fresh copy of Fedora 39 on my NVME SSD and copied all the configurations from my previous install from my SATA SSD, that I used related to the kernel and nvidia drivers.

Strangely, when trying boot to Gnome login screen, the screen freezes, it only works when I uncomment the WaylandEnable=false line inside /etc/gdm/custom.conf. Which IS NOT needed on my original install on the exact same machine. (had the same problem with Silverblue and tought it was Silverblue then I installed Fedora Workstation)

I really don’t get what is happening. Any ideas?

Tested with Kernel 6.7.3-200 and 6.7.2-cb2.0 (cachyos) using NVIDIA drivers version 545.29.06

The only thing I found that is different is /etc/X11/xorg.conf.d/00-keyboard.conf file. Why? Dunno

It sounds like a potential regression with the nvidia drivers on 6.7.3 with Wayland. Are you able to get any logs from journalctl that might give a clue as to the freezing?

Was not working with 6.7.3 and 6.7.2 form cachyos, but are working with those same kernels on my old installation. But it’s solved now. I just got it working literally 10 minutes ago.
Luckily I havent formatted the SATA drive yet. I decided to check some packages with dnf history. There were some that I did not install, because I was not using, but some related to vulkan/mesa I forgot to install and also on the list was egl-wayland which I guess is the one the solved the problem:

egl-wayland-1.1.13-1.fc39.x86_64
egl-wayland-devel-1.1.13-1.fc39.x86_64
libwayland-client-1.22.0-2.fc39.i686
libwayland-cursor-1.22.0-2.fc39.i686
libwayland-egl-1.22.0-2.fc39.i686
libwayland-server-1.22.0-2.fc39.i686
mesa-demos-9.0.0-3.fc39.x86_64
mesa-dri-drivers-1:23.3.3-1.fc39.i686
mesa-filesystem-1:23.3.3-1.fc39.i686
mesa-libEGL-1:23.3.3-1.fc39.i686
mesa-libGL-1:23.3.3-1.fc39.i686
mesa-libGLU-9.0.3-1.fc39.x86_64
mesa-libOSMesa-1:23.3.3-1.fc39.x86_64
mesa-libOpenCL-1:23.3.3-1.fc39.x86_64
mesa-libOpenCL-devel-1:23.3.3-1.fc39.x86_64
mesa-libgbm-1:23.3.3-1.fc39.i686
mesa-libglapi-1:23.3.3-1.fc39.i686
mesa-va-drivers-1:23.3.3-1.fc39.i686
mesa-vdpau-drivers-1:23.3.3-1.fc39.i686
mesa-vdpau-drivers-1:23.3.3-1.fc39.x86_64
mesa-vulkan-drivers-1:23.3.3-1.fc39.i686
vulkan-loader-1.3.268.0-1.fc39.i686
vulkan-tools-1.3.268.0-1.fc39.x86_64
wayland-devel-1.22.0-2.fc39.x86_64

Shouldn’t egl-wayland be installed by default? (assuming that from that list is the right one that solved it)

1 Like

Did the tests again and it is really egl-wayland, but is not a problem perse since I do not use RPMFusion’s nvidia drivers, I use Negativo17’s. It never happenend before because before doing anything I run my installation script on a new installation. But in this case, I was doing a fresh install for testing if I would start using Fedora Silverblue or keep using Fedora Workstation. As the GDM login bug happened with Silverblue first, I thought it was something with Silverblue not dealing well with Negativo’s repo, but installing Workstation, I saw that the same happened. I even installed twice since I downloaded the most updated ISO from the Respins and thought it could have a similar problem with the repo, but wasn’t the case, both Workstation ISOs presented the same problem.
RPMFusion installs egl-wayland when install the nvidia drivers, Negativo17’s at least used to, but