gnome session is logged out after resuming from suspend.

odror · 2026-04-23 23:09:01

I do not know if I am getting the same crash, but my crash seems to be related to mutter and some hardware race condition that it cannot handle well.

Is there a way to tell wayland the EDID of a monitor as it is done in x11. That might help. I just realize that I do not know how to get the EDID of a monitor when I am on wayland.

seth · 2026-04-24 08:32:30

Apr 22 19:55:49 i9-13900k-arch kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
Apr 22 19:55:49 i9-13900k-arch kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
Apr 22 19:55:49 i9-13900k-arch kernel: nvidia 0000:01:00.0: [drm] User-defined mode not supported: "1920x1080": 60 172780 1920 2040 2248 2576 1080 1081 1084 1118 0x20 0x6
Apr 22 19:55:49 i9-13900k-arch kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
Apr 22 19:55:49 i9-13900k-arch kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
Apr 22 19:55:49 i9-13900k-arch kernel: nvidia 0000:01:00.0: [drm] User-defined mode not supported: "1920x1080": 60 172780 1920 2040 2248 2576 1080 1081 1084 1118 0x20 0x6
Apr 22 19:55:50 i9-13900k-arch gnome-shell[227774]: Page flip failed: drmModeAtomicCommit: Invalid argument
Apr 22 19:55:50 i9-13900k-arch gnome-shell[227774]: Page flip failed: drmModeAtomicCommit: Invalid argument
Apr 22 19:55:50 i9-13900k-arch gnome-shell[227774]: Page flip failed: drmModeAtomicCommit: Invalid argument
Apr 22 19:55:50 i9-13900k-arch gnome-shell[227774]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
…
Apr 22 19:55:51 i9-13900k-arch kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
Apr 22 19:55:51 i9-13900k-arch kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
Apr 22 19:55:51 i9-13900k-arch kernel: nvidia 0000:01:00.0: [drm] User-defined mode not supported: "1920x1080": 60 172780 1920 2040 2248 2576 1080 1081 1084 1118 0x20 0x6
Apr 22 19:55:51 i9-13900k-arch audit[227774]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=4 pid=227774 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
Apr 22 19:55:51 i9-13900k-arch kernel: gnome-shell[227774]: segfault at 1c ip 00007f682764d4d1 sp 00007ffc87b0bac0 error 4 in libmutter-18.so.0.0.0[19d4d1,7f68274ed000+1e7000] likely on CPU 4 (core 8, socket 0)
Apr 22 19:55:51 i9-13900k-arch kernel: Code: 83 ec 68 48 63 05 1f ff 14 00 89 4d cc 4c 89 45 90 4c 8b 6c 02 40 ff 15 75 80 14 00 48 63 0d 06 ff 14 00 49 8b 7f 58 89 45 b0 <41> 8b 45 1c 48 01 d9 89 45 c0 41 8b 45 20 48 8b 51 30 89 45 b8 41
Apr 22 19:55:51 i9-13900k-arch kernel: audit: error in audit_log_subj_ctx
Apr 22 19:55:51 i9-13900k-arch systemd-coredump[238770]: Process 227774 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Apr 22 19:55:51 i9-13900k-arch audit: BPF prog-id=589 op=LOAD
Apr 22 19:55:51 i9-13900k-arch audit: BPF prog-id=590 op=LOAD
Apr 22 19:55:51 i9-13900k-arch audit: BPF prog-id=591 op=LOAD
Apr 22 19:55:51 i9-13900k-arch systemd[1]: Started Process Core Dump (PID 238770/UID 0).
Apr 22 19:55:51 i9-13900k-arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@64-69644-238770_238771-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 22 19:55:51 i9-13900k-arch audit: BPF prog-id=592 op=LOAD
Apr 22 19:55:51 i9-13900k-arch audit: BPF prog-id=593 op=LOAD
Apr 22 19:55:51 i9-13900k-arch audit: BPF prog-id=594 op=LOAD
Apr 22 19:55:51 i9-13900k-arch systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Apr 22 19:55:51 i9-13900k-arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=drkonqi-coredump-processor@64-69644-238770_238771-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 22 19:55:51 i9-13900k-arch avahi-daemon[2648]: Leaving mDNS multicast group on interface br0.IPv6 with address fe80::4025:aff:fe74:926c.
Apr 22 19:55:51 i9-13900k-arch avahi-daemon[2648]: Joining mDNS multicast group on interface br0.IPv6 with address fd6c:280e:4efa:eaae:4025:aff:fe74:926c.
Apr 22 19:55:51 i9-13900k-arch avahi-daemon[2648]: Registering new address record for fd6c:280e:4efa:eaae:4025:aff:fe74:926c on br0.*.
Apr 22 19:55:51 i9-13900k-arch avahi-daemon[2648]: Withdrawing address record for fe80::4025:aff:fe74:926c on br0.
Apr 22 19:55:51 i9-13900k-arch systemd-coredump[238771]: Process 227774 (gnome-shell) of user 1000 dumped core.
                                                         
                                                         Stack trace of thread 227774:
                                                         #0  0x00007f682764d4d1 n/a (libmutter-18.so.0 + 0x19d4d1)
                                                         #1  0x00007f682764dbc6 n/a (libmutter-18.so.0 + 0x19dbc6)
                                                         #2  0x00007f6827c7fa0c g_closure_invoke (libgobject-2.0.so.0 + 0x11a0c)
                                                         #3  0x00007f6827c9ee97 n/a (libgobject-2.0.so.0 + 0x30e97)
                                                         #4  0x00007f6827ca090f n/a (libgobject-2.0.so.0 + 0x3290f)
                                                         #5  0x00007f6827ca0b89 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32b89)
                                                         #6  0x00007f6827ca0c44 g_signal_emit (libgobject-2.0.so.0 + 0x32c44)
                                                         #7  0x00007f682755f65d n/a (libmutter-18.so.0 + 0xaf65d)
                                                         #8  0x00007f682755fad1 meta_monitor_manager_rebuild (libmutter-18.so.0 + 0xafad1)
                                                         #9  0x00007f682768ca3a n/a (libmutter-18.so.0 + 0x1dca3a)
                                                         #10 0x00007f6827554eab meta_monitor_manager_ensure_configured (libmutter-18.so.0 + 0xa4eab)
                                                         #11 0x00007f682768be00 n/a (libmutter-18.so.0 + 0x1dbe00)
                                                         #12 0x00007f6827c7fa0c g_closure_invoke (libgobject-2.0.so.0 + 0x11a0c)
                                                         #13 0x00007f6827c9e8ab n/a (libgobject-2.0.so.0 + 0x308ab)
                                                         #14 0x00007f6827ca090f n/a (libgobject-2.0.so.0 + 0x3290f)
                                                         #15 0x00007f6827ca0b89 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32b89)
                                                         #16 0x00007f6827ca0c44 g_signal_emit (libgobject-2.0.so.0 + 0x32c44)
                                                         #17 0x00007f68276ab0f8 n/a (libmutter-18.so.0 + 0x1fb0f8)
                                                         #18 0x00007f6827c7e50b g_cclosure_marshal_VOID__OBJECTv (libgobject-2.0.so.0 + 0x1050b)
                                                         #19 0x00007f6827ca0a77 n/a (libgobject-2.0.so.0 + 0x32a77)
                                                         #20 0x00007f6827ca0b89 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32b89)
                                                         #21 0x00007f6827ca0c44 g_signal_emit (libgobject-2.0.so.0 + 0x32c44)
                                                         #22 0x00007f68276cb3a6 n/a (libmutter-18.so.0 + 0x21b3a6)
                                                         #23 0x00007f6826795ac6 n/a (libffi.so.8 + 0x7ac6)
                                                         #24 0x00007f682679276b n/a (libffi.so.8 + 0x476b)
                                                         #25 0x00007f682679506e ffi_call (libffi.so.8 + 0x706e)
                                                         #26 0x00007f6827c86370 g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x18370)
                                                         #27 0x00007f6827c7fa0c g_closure_invoke (libgobject-2.0.so.0 + 0x11a0c)
                                                         #28 0x00007f6827c9e8ab n/a (libgobject-2.0.so.0 + 0x308ab)
                                                         #29 0x00007f6827ca090f n/a (libgobject-2.0.so.0 + 0x3290f)
…

Looks like, might be related to https://gitlab.gnome.org/GNOME/mutter/-/issues/4369
Try to get the debuginfod enriched https://wiki.archlinux.org/title/Core_d … _core_dump

Is there a way to tell wayland the EDID of a monitor as it is done in x11

There's no "wayland", you'd have to tell gnome - I doubt this is possible but you can generally inject an edid: https://wiki.archlinux.org/title/Kernel … s_and_EDID

odror · 2026-04-25 21:56:12

That bug was closed with a patch to 49.2. This bug started in my system at the end of 49 cycle and now continuing to version 50. It is my opinion that the gnome team rushed to end x11 support, while wayland is not fully mature for gnome, unlike plasma where there are no major issues for me. Here is another big issue for gnome+wayland. It does not support more than 4 4k monitors, unlike plasma and and cosmic desktops.

seth · 2026-04-26 08:36:50

It is my opinion that the gnome team rushed to end x11 support

You don't want to hear my opnion about the gnome team, but that's irrelevant if you desire to use gnome.

I know that that particular bug was "fixed", the open question is about the quality of the fix.
https://wiki.archlinux.org/title/Core_d … _core_dump - say "y" when it asks you for debuginfod.

Did you try to inject an edid?

odror · 2026-04-26 16:37:19

This is the /proc/cmdline with the edid. It did not make a difference. It is amazing how smooth and fast plasma+gdm wakeup is (even with 5 4k monitors). gnome takes longer and it fails.

"root=ZFS=apool/root rw zfs_import_dir=/dev/ intel_iommu=on iommu=pt kvm.ignore_msrs=1 nvidia-drm.modeset=1 nvidia-drm.fbdev=1 apparmor=1 security=apparmor pcie_ptm=off nvidia.NVreg_PreserveVideoMemoryAllocations=1 nvidia.NVreg_TemporaryFilePath=/var/tmp nvidia.NVreg_EnableMSI=1 drm.edid_firmware=HDMI-A-5:edid/hdmia5.bin drm.edid_firmware=DP-5:edid/dp5.bin

seth · 2026-04-26 16:51:14

The question is whether it's also loaded.
Can we please see the debuginfod enhaced coredump?

It is amazing how smooth and fast plasma+gdm wakeup is (even with 5 4k monitors). gnome takes longer and it fails.

You don't have to sell me to not using gnome…

Arch Linux

#26 2026-04-23 23:09:01

Re: gnome session is logged out after resuming from suspend.

#27 2026-04-24 08:32:30

Re: gnome session is logged out after resuming from suspend.

#28 2026-04-25 21:56:12

Re: gnome session is logged out after resuming from suspend.

#29 2026-04-26 08:36:50

Re: gnome session is logged out after resuming from suspend.

#30 2026-04-26 16:37:19

Re: gnome session is logged out after resuming from suspend.

#31 2026-04-26 16:51:14

Re: gnome session is logged out after resuming from suspend.

Board footer