GNOME 48 resuming from suspend on Tumbleweed causes SEGFAULT in mutter and coredump resulting in current session loss

Hi,

I have recently moved onto Gnome 48 from 47 on Tumbleweed. This issue was not there on 47 but started occurring on 48.

Issue: Resuming after suspend results in gnome-shell segfault due to error in libmutter which results in gnome-shell core dump, losing the current session and starting a new session.

Below are the journalctl logs

process log
gnome-shell[3334]: (…/src/backends/meta-output.c:144):meta_output_get_monitor: runtime check failed: (priv->monitor)
kernel: gnome-shell[3334]: segfault at ffffffffffffffe8 ip 00007ff4f3eb0f87 sp 00007ffc4ce8a6d8 error 5 in libmutter-16.so.0.0.0[b0f87,7ff4f3e6b000+175000] likely on CPU 4 (core 2, socket 0)
kernel: Code: 0c f3 0f 10 0d 6e 18 16 0 0f 2f c8 0f 87 23 ff ff ff eb b8 e8 4a 7 fc ff 66 2e 0f 1f 84 0 0 0 0 0 48 63 5 e1 b0 1e 0 <8b> 44 38 48 c3 0f 1f 40 0 48 8b 47 20 c3 66 66 2e 0f 1f 84 0 0
systemd-coredump[27736]: Process 3334 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing…
systemd[1]: Started Process Core Dump (PID 27736/UID 0).
systemd-coredump[27737]: Process 3334 (gnome-shell) of user 1000 dumped core.
discord.desktop[5293]: 05:50:46.577 › [GatewaySocket] Setting connection state to CONNECTING
discord.desktop[5293]: 05:50:46.577 › [GatewaySocket] [CONNECT] wss://gateway.discord.gg, encoding: etf, version: 9, compression: zstd-stream
systemd[1]: systemd-coredump@3-27736-0.service: Deactivated successfully.
systemd[1]: systemd-coredump@3-27736-0.service: Consumed 1.570s CPU time.
kitty.desktop[11959]: [441.239] [glfw error 65544]: Wayland: fatal display error: Broken pipe
xdg-desktop-por[4098]: Lost connection to Wayland compositor.
gnome-software[3566]: Lost connection to Wayland compositor.
xdg-desktop-por[4263]: Error reading events from display: Broken pipe
evolution-alarm[3591]: Error reading events from display: Broken pipe
gsd-wacom[3599]: Error reading events from display: Broken pipe
gsd-power[3550]: Error reading events from display: Broken pipe
gsd-media-keys[3549]: Error reading events from display: Broken pipe
gsd-color[3540]: Error reading events from display: Broken pipe
systemd[2483]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE
systemd[2483]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE
systemd[2483]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE
systemd[2483]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE
systemd[2483]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE
systemd[2483]: xdg-desktop-portal-gnome.service: Failed with result ‘exit-code’.
systemd[2483]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
systemd[2483]: xdg-desktop-portal-gtk.service: Failed with result ‘exit-code’.
gsd-keyboard[3544]: Error reading events from display: Broken pipe
gnome-shell[3773]: (EE) failed to read Wayland events: Broken pipe
evolution[5148]: Error reading events from display: Broken pipe
WebKitWebProces[5208]: Error reading events from display: Broken pipe
polkitd[1363]: Unregistered Authentication Agent for unix-session:4 (system bus name :1.79, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
discord.desktop[5422]: XIO: fatal IO error 13 (Permission denied) on X server :0
discord.desktop[5422]: after 96 requests (96 known processed) with 0 events remaining.
systemd[2483]: kitty-11959-0.scope: Consumed 2.620s CPU time.
systemd[2483]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE
systemd[2483]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result ‘exit-code’.
systemd[2483]: org.gnome.SettingsDaemon.Color.service: Failed with result ‘exit-code’.
systemd[2483]: org.gnome.SettingsDaemon.Power.service: Failed with result ‘exit-code’.
systemd[2483]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV
systemd[2483]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result ‘exit-code’.
systemd[2483]: org.gnome.SettingsDaemon.XSettings.service: Failed with result ‘exit-code’.
systemd[2483]: app-gnome-org.gnome.Evolution-5148.scope: Consumed 28.617s CPU time.
systemd[2483]: org.gnome.Shell@wayland.service: Failed with result ‘core-dump’.
systemd[2483]: org.gnome.Shell@wayland.service: Consumed 4min 59.500s CPU time.
systemd[2483]: org.gnome.Shell@wayland.service: Triggering OnFailure= dependencies.
systemd[2483]: org.gnome.Shell@wayland.service: Failed to enqueue OnFailure=org.gnome.Shell-disable-extensions.service job, ignoring: Unit org.gnome.Shell-disable-extensions.service has a bad unit file setting.
systemd[2483]: Stopped target GNOME Wayland Session (session: gnome).
systemd[2483]: Stopped target Current graphical user session.
systemd[2483]: Stopped target GNOME Session.
systemd[2483]: Stopped target GNOME Wayland Session.
systemd[2483]: Stopped target GNOME session X11 services.
systemd[2483]: Stopped target GNOME Session (session: gnome).
systemd[1]: run-user-1000-doc.mount: Deactivated successfully.
systemd[2483]: Stopped GNOME Session Manager (session: gnome).
systemd[2483]: Stopped target Tasks to be run before GNOME Session starts.
systemd[2483]: Stopped target Session services which should run early before the graphical session is brought up.
systemd[2483]: Reached target Shutdown running GNOME Session.
systemd[2483]: Stopping Monitor Session leader for GNOME Session…
systemd[2483]: Starting Restart DBus after GNOME Session shutdown…
systemd[2483]: Stopped target Shutdown running GNOME Session.
systemd[2483]: Stopped Monitor Session leader for GNOME Session.
systemd[2483]: Started Restart DBus after GNOME Session shutdown.
gnome-session-c[27945]: Failed to restart DBus service: GDBus.Error:org.freedesktop.systemd1.OnlyByDependency: Operation refused, unit dbus-broker.service may be requested by dependency only (it is configured to refuse manual start/stop).
systemd[1]: session-4.scope: Deactivated successfully.
systemd-logind[1380]: Session 4 logged out. Waiting for processes to exit.
systemd-logind[1380]: Removed session 4
systemd-logind[1380]: New session c11 of user gdm.
systemd[1]: Created slice User Slice of UID 459
systemd[1]: Starting User Runtime Directory /run/user/459…
systemd[1]: Finished User Runtime Directory /run/user/459.
systemd[1]: Starting User Manager for UID 459…
systemd-logind[1380]: New session 15 of user gdm.

Please check that you have mutter version 48.0+5-1.1
If not so, upgrade your system (zypper dup) and try again.
A similar thread here

Yes, i do have the latest version of mutter and have gone through that thread, however I am still having the issue.

`Information for package mutter:

Repository : Main Repository (OSS)
Name : mutter
Version : 48.0+5-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 5.2 MiB
Installed : Yes (automatically)
Status : up-to-date
Source package : mutter-48.0+5-1.1.src
Upstream URL : https://www.gnome.org
Summary : Window and compositing manager based on Clutter
Description :
Mutter is a window and compositing manager based on Clutter, forked
from Metacity.`

@dance_monki Hi and welcome to the Forum :smile:
Can you paste the output from inxi -SGaz

Hi, pleasure to be here.

Output of inxi -SGaz:

System:
  Kernel: 6.13.7-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: hpet avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.13.7-1-default
    root=UUID=cb98a71d-3462-400f-aaa2-2086dd40b930 splash=silent amd_iommu=on
    resume=/dev/disk/by-uuid/023799da-2b98-4234-a2f9-c7be3fc95892
    mitigations=auto quiet security=apparmor rd.driver.blacklist=nouveau
  Desktop: GNOME v: 48.0 tk: GTK v: 3.24.49 wm: gnome-shell
    tools: gsd-screensaver-proxy avail: xscreensaver dm: 1: GDM v: 48.0 2: SDDM
    note: stopped Distro: openSUSE Tumbleweed 20250324
Graphics:
  Device-1: NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q] vendor: ASUSTeK
    driver: nvidia v: 570.133.07 alternate: nouveau,nvidia_drm
    non-free: 550/565.xx+ status: current (as of 2025-01; EOL~2026-12-xx)
    arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-2023 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: none empty: DP-1,DP-2 bus-ID: 01:00.0 chip-ID: 10de:249d
    class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Cezanne [Radeon Vega Series /
    Radeon Mobile Series] vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5
    code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s
    lanes: 16 ports: active: HDMI-A-1 off: eDP-1 empty: none bus-ID: 06:00.0
    chip-ID: 1002:1638 class-ID: 0300 temp: 58.0 C
  Device-3: Lenovo FHD Webcam driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.2:6
    chip-ID: 17ef:4831 class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6
    compositor: gnome-shell driver: X: loaded: modesetting,nvidia unloaded: vesa
    alternate: fbdev,nouveau,nv dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: HDMI-1 model: GSM LG ULTRAGEAR res: mode: 1920x1080 hz: 144
    scale: 100% (1) dpi: 92 size: 530x300mm (20.87x11.81") diag: 609mm (23.98")
    modes: N/A
  Monitor-2: HDMI-A-1 model: LG (GoldStar) ULTRAGEAR serial: <filter>
    built: 2022 res: 1920x1080 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65")
    diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  Monitor-3: eDP-1 model: ChiMei InnoLux 0x1540 built: 2020 res: 2560x1440
    dpi: 189 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
    ratio: 16:9 modes: max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
    drv: nvidia device: 1 drv: radeonsi gbm: drv: kms_swrast surfaceless:
    drv: nvidia wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 25.0.2 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM
    3.61 6.13.7-1-default) device-ID: 1002:1638 memory: 500 MiB unified: no
    display-ID: :0.0
  API: Vulkan v: 1.4.309 layers: 2 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: N/A device-ID: 1002:1638
    surfaces: xcb,xlib,wayland device: 1 type: discrete-gpu name: NVIDIA
    GeForce RTX 3070 Laptop GPU driver: N/A device-ID: 10de:249d
    surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-doctor
    gpu: nvidia-settings, nvidia-smi, radeontop wl: wayland-info
    x11: xdpyinfo, xprop, xrandr

@dance_monki So dual graphics Nvidia and AMD, a laptop and your running the laptop with the lid closed and a monitor connected to the AMD gpu?

@malcolmlewis Yes, Asus gaming laptop with amd igpu and nvidia dgpu. Running with closed laptop lid connected to an external monitor on wayland gnome on AMD.

@dance_monki So this doesn’t duplicate if just with the laptop open and displayed on the internal screen, no monitor attached?

@malcolmlewis
Never thought of this, I have just checked now, removing the external monitor.
While the external monitor is not connected, everything is working fine.
Resuming from suspend is leading to the issue/ error only while the monitor is connected irrespective of laptop lid/ screen being on/ off.

@dance_monki Are you running the experimental VRR feature , I suspect the 144Hz can be changed on that external monitor too?

@malcolmlewis No, I am not using the experimental VRR. Even in the display settings I don’t see any VRR toggle option, so it is not enabled. My monitors are set to constant refresh rate but one is 165Hz and the other is 144Hz.

@dance_monki can you set both the same and see if that helps?

@malcolmlewis

I have tried doing multiple things: same refresh rate, one connected while the other is closed, changing primary displays, mirroring instead of joining… nothing is reliably working apart from using the standalone laptop display without connecting to the external monitor

Also I sometimes used to (even now) get this, while on lock/ sleep, if this has anything to do with.

@dance_monki your using grub or systemd-boot on this system? As a test can you add amdgpu.dcdebugmask=0x10 to the kernel boot options.

@malcolmlewis I am using grub. I added it to the kernel boot options
output of dmesg | grep -i dcdebug:

[    0.000000] [      T0] Command line: BOOT_IMAGE=/boot/vmlinuz-6.13.7-1-default root=UUID=cb98a71d-3462-400f-aaa2-2086dd40b930 splash=silent amdgpu.dcdebugmask=0x10 amd_iommu=on resume=/dev/disk/by-uuid/023799da-2b98-4234-a2f9-c7be3fc95892 mitigations=auto quiet security=apparmor rd.driver.blacklist=nouveau
[    0.013083] [      T0] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.13.7-1-default root=UUID=cb98a71d-3462-400f-aaa2-2086dd40b930 splash=silent amdgpu.dcdebugmask=0x10 amd_iommu=on resume=/dev/disk/by-uuid/023799da-2b98-4234-a2f9-c7be3fc95892 mitigations=auto quiet security=apparmor rd.driver.blacklist=nouveau

However, it did not get fixed

@dance_monki Ok, well remove then… so the monitor connection and laptop connection types are?

@malcolmlewis External monitor is connected through HDMI and laptop is edp1, if that’s what you are referring to…

@dance_monki Is there a Display Port connector? I’m assuming the HDMI cable is the correct specification etc?

Can you show the output fromxrandr --listmonitors

What happens if you add the kernel boot option amdgpu.dc=0

@malcolmlewis
xrandr --listmonitors

Monitors: 2
 0: +*HDMI-1 1920/530x1080/300+2560+360  HDMI-1
 1: +eDP-1 2560/340x1440/190+0+0  eDP-1

I tried the amdgpu.dc=0 boot option but on rebooting, the system froze before booting. I tried restarting multiple times and checked but to no avail, it froze every time after uefi and while booting at the start itself (before/after grub ig). Couldn’t even open grub menu. I had to make a live usb, chroot and change things back.

@dance_monki Crazy… you can add at boot via pressing the ‘e’ key and arrow down to the linux/linuxefi line, press end add the option and hit F10 to boot :wink:

So it’s some sort of AMD GPU and it’s HDMI connection bug/regression. Maybe it’s the monitor. You wouldn’t have a test monitor or perhaps a TV to try it on to see?