gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer()

[Matthew M. Dean]

When using Wayland on Ubuntu 22.04 gnome-shell is crashing anytime you leave the Desktop and return to the login screen.

dmesg -
[ 6522.928409] gnome-shell[20890]: segfault at 20 ip 0000000000000020 sp 00007ffe402baef8 error 14
[ 6522.928414] Code: Unable to access opcode bytes at RIP 0xfffffffffffffff6.

gdb -
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x00007f4e2b0070d7 in gbm_surface_release_buffer () from /lib/x86_64-linux-gnu/libgbm.so.1

(gdb) backtrace
#0 0x00007f93da12d0d7 in gbm_surface_release_buffer () at /lib/x86_64-linux-gnu/libgbm.so.1
#1 0x00007f93dc4e48ff in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#2 0x00007f93dd1f8dfd in g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3 0x00007f93dc4edd40 in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#4 0x00007f93dd0d5698 in g_hash_table_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f93dc4f9fcc in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#6 0x00007f93dc5141ae in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#7 0x00007f93dc4fa03d in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#8 0x00007f93dd0f1c24 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x00007f93dd1466f8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f93dd0f1293 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f93dc462209 in meta_context_run_main_loop () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#12 0x000056280e1b6ed2 in ()
#13 0x00007f93dc193d90 in __libc_start_call_main (main=main@entry=0x56280e1b6a30, argc=argc@entry=1, argv=argv@entry=0x7ffc82080608) at ../sysdeps/nptl/libc_start_call_main.h:58
#14 0x00007f93dc193e40 in __libc_start_main_impl (main=0x56280e1b6a30, argc=1, argv=0x7ffc82080608, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc820805f8) at ../csu/libc-start.c:392
#15 0x000056280e1b7155 in ()

Also Wayland shows my monitors backwards, left on the right, right on the left. Works fine in Xorg.

If i try to rearrange the physical displays of my 2 monitors, I get kicked out when pressing apply.
dmesg -
[ 7618.079350] traps: gnome-shell[25726] general protection fault ip:7f34373be0d7 sp:7ffcfb2a9538 error:0 in libgbm.so.1.0.0[7f34373b7000+8000]

System:
  Host: desktop Kernel: 5.17.0-1003-oem x86_64 bits: 64 compiler: gcc
    v: 11.2.0 Desktop: GNOME 42.0 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3
    Distro: Ubuntu 22.04 (Jammy Jellyfish)
CPU:
  Info: quad core model: Intel Core i5-7600K bits: 64 type: MCP
    arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 4401 high: 4404 min/max: 800/4400 cores: 1: 4401
    2: 4400 3: 4400 4: 4404 bogomips: 30399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
    ports: active: HDMI-A-3 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:5912
  Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
    vendor: Sapphire driver: amdgpu v: kernel pcie: speed: 2.5 GT/s lanes: 16
    ports: active: HDMI-A-5 empty: DP-3, DP-4, DVI-D-1, HDMI-A-4
    bus-ID: 01:00.0 chip-ID: 1002:67df
  Device-3: Logitech HD Webcam C615 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:082c
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: radeon
    gpu: amdgpu,i915 display-ID: 0
  Monitor-1: HDMI-A-3 model: Asus VG23A res: 1920x1080 dpi: 91
    diag: 618mm (24.3")
  Monitor-2: HDMI-A-5 model: Samsung res: 1920x1080 dpi: 44
    diag: 1271mm (50.1")
  OpenGL: renderer: AMD Radeon RX 580 Series (polaris10 LLVM 14.0.0 DRM
    3.44 5.17.0-1003-oem)
    v: 4.6 Mesa 22.1.0-devel direct render: Yes

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1969351/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Daniel van Vugt (vanvugt)]

Please update your system:

  sudo apt update
  sudo apt full-upgrade

and then ensure you have these debug symbols installed before getting a stack trace from gdb:

  https://launchpad.net/ubuntu/+archive/primary/+files/libmutter-10-0-dbgsym_42.0-3ubuntu2_amd64.ddeb

Alternatively just follow the instructions in https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Please also run this command to gather more system info:

  apport-collect 1969351

[Daniel van Vugt (vanvugt)]

Actually it looks like:

  https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4

in which case we may not need any more info.

[Daniel van Vugt (vanvugt)]

We can use bug 1969422 to track it now.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.