Wayland won't start after update of GNOME 40, X11 is loaded instead


I seem to have a problem with Wayland for some reason after updating today, the system is stuck in the booting screen for about a minute and after the login screen finally appears I saw in the settings that it’s using X11. In the logs I saw that it says the following:

gkr-pam: unable to locate daemon control file

Has anybody else experienced this? Is there a known fix? I’ll be happy to provide additional information if needed. I’m not using NVIDIA btw, my laptop has only Intel Xe integrated graphics.

Thanks in advance!

Welcome to the community @taylenismable.

Yes we would like more info’s. What kind of update you made? Was it a kernel update? If yes try an older kernel pressing ESC while booting.

There wasn’t any new kernels among the updates - there was mutter (for sure) and maybe gnome-shell or something else gnome-related, which I suspect may have caused it.

You don’t happen to be using fish do you?


May want to check some of the things here as well.

I don’t even know what that is, so I don’t think I’m using it.

Looking at the logs I also found these messages from systemd, not sure if it helps at all:
org.gnome.Shell@wayland.service: Skipped due to ‘exec-condition’.
org.gnome.Shell@wayland.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Condition check resulted in GNOME Shell on Wayland being skipped.