Comment 9 for bug 2034619

Hello Daniel and thanks for the help.
I attach two logs, both after a fresh reboot. The first (_lock) is when locking with win-L, the second after 1 minute screen blank (_blank. I have set it not to automatically lock at screen blank. Both cause wayland to crash and I return to the gdm with the session ended. There is of course some overlap in the logs.

I'm not an expert as you, but very curious as to what's causing it. There is at least some indication of a wayland crash...

Sep 07 09:09:41 ThinkPad-P14s-Gen-3 systemd[3855]: Started snap.snapd-desktop-integration.snapd-desktop-integration.service - Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Sep 07 09:09:41 ThinkPad-P14s-Gen-3 gnome-shell[3352]: Connection to xwayland lost
Sep 07 09:09:41 ThinkPad-P14s-Gen-3 gnome-shell[3352]: Xwayland terminated, exiting since it was mandatory
Sep 07 09:09:41 ThinkPad-P14s-Gen-3 gnome-shell[3352]: (../src/core/meta-context.c:533):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop))
Sep 07 09:09:41 ThinkPad-P14s-Gen-3 systemd[3855]: Started tracker-miner-fs-3.service - Tracker file system data miner.
Sep 07 09:09:41 ThinkPad-P14s-Gen-3 gnome-shell[3352]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly
                                                       @resource:///org/gnome/shell/ui/init.js:21:20
Sep 07 09:09:41 ThinkPad-P14s-Gen-3 gnome-shell[3352]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
Sep 07 09:09:41 ThinkPad-P14s-Gen-3 gdm-launch-environment][3244]: pam_unix(gdm-launch-environment:session): session closed for user gdm