I appear to be hitting a regression after installing mesa 26.0.8-1ubuntu0.1 from resolute-proposed.
The system was upgraded on 2026-06-05 at 17:34:56 EDT: libgl1-mesa-dri: 26.0.3-1ubuntu1 -> 26.0.8-1ubuntu0.1 libglx-mesa0: 26.0.3-1ubuntu1 -> 26.0.8-1ubuntu0.1 libegl-mesa0: 26.0.3-1ubuntu1 -> 26.0.8-1ubuntu0.1 libgbm1: 26.0.3-1ubuntu1 -> 26.0.8-1ubuntu0.1 mesa-libgallium: 26.0.3-1ubuntu1 -> 26.0.8-1ubuntu0.1 mesa-vulkan-drivers: 26.0.3-1ubuntu1 -> 26.0.8-1ubuntu0.1 After the upgrade, GNOME Shell crashed twice during normal use of Chrome/Teams video with OBS virtual camera active. The machine did not reboot; only the graphical session/compositor died and GDM restarted the session. Crash timestamps: 2026-06-08 09:08:53 EDT: gnome-shell[5414]: GNOME Shell crashed with signal 11 systemd: [email protected]: Main process exited, code=dumped, status=11/SEGV systemd: [email protected]: Failed with result 'core-dump' 2026-06-08 09:10:50 EDT: gnome-shell[1652369]: GNOME Shell crashed with signal 11 systemd: [email protected]: Main process exited, code=dumped, status=11/SEGV systemd: [email protected]: Failed with result 'core-dump' Observed trigger pattern: - GNOME on Wayland. - Google Chrome running Microsoft Teams video. - OBS Studio running on Wayland. - OBS virtual camera active. - Chrome logged WebRTC/OpenH264/H.264 decoder warnings/errors immediately before the second crash: - OpenH264 warning about actual input framerate 0.000000. - h264_decoder_impl.cc:411 avcodec_receive_frame error: -11. - OBS logged that the Wayland compositor died: - "The Wayland connection broke during blocking read event. Did the Wayland compositor die?" OBS log correlation: First crash: OBS virtual camera started at 2026-06-08 08:59:30 EDT. GNOME Shell crashed at 2026-06-08 09:08:53 EDT. Second crash: OBS virtual camera started at 2026-06-08 09:10:14 EDT. GNOME Shell crashed at 2026-06-08 09:10:50 EDT. Core dump backtrace excerpt from /var/crash/_usr_bin_gnome- shell.1000.crash: Core was generated by `/usr/bin/gnome-shell --mode=ubuntu'. Program terminated with signal SIGSEGV, Segmentation fault. #6 0x000070ad779feb04 in gbm_bo_destroy () from /usr/lib/x86_64-linux-gnu/libgbm.so.1 #7 0x000070ad6d77f06a in ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 #8 0x000070ad6d77f0b9 in ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 #9 0x000070ad51383531 in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.0.8-1ubuntu0.1.so #10 0x000070ad513835d3 in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.0.8-1ubuntu0.1.so #15 0x000070ad5137e242 in driBindContext () from /usr/lib/x86_64-linux-gnu/libgallium-26.0.8-1ubuntu0.1.so #16 0x000070ad6d77ab64 in ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 #17 0x000070ad6d76c1c9 in ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 #18 0x000070ad7a516745 in ?? () from /usr/lib/x86_64-linux-gnu/libEGL.so.1 #19 0x000070ad7ae90ffd in _cogl_winsys_egl_make_current () from /usr/lib/x86_64-linux-gnu/mutter-18/libmutter-cogl-18.so.0 #20 0x000070ad7ae928ab in ?? () from /usr/lib/x86_64-linux-gnu/mutter-18/libmutter-cogl-18.so.0 #21 0x000070ad7b5d1b79 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-18.so.0 #22 0x000070ad7b5e54fd in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-18.so.0 #26 0x000070ad7b50164a in meta_context_run_main_loop () from /usr/lib/x86_64-linux-gnu/libmutter-18.so.0 System/package details: Ubuntu 26.04 resolute Kernel: 7.0.0-22-generic GNOME Shell: 50.1-0ubuntu1 Mutter: libmutter-18-0 50.1-0ubuntu2.1 Mesa packages: 26.0.8-1ubuntu0.1 from resolute-proposed Chrome: google-chrome-stable 149.0.7827.53-1 OBS: obs-studio 32.1.2-0obsproject2~resolute PipeWire: 1.6.2-1ubuntu1 WirePlumber: 0.5.13-1ubuntu1 GPU: Intel Corporation Arrow Lake-S [Intel Graphics] [8086:7d67] rev 06 Kernel driver in use: i915 Kernel modules: i915, xe Notes: - This began after installing the Mesa 26.0.8 proposed packages on Friday, 2026-06-05. The machine had little use between the upgrade and these crashes. - The crash stack directly involves libgbm/libEGL_mesa/libgallium from the upgraded package set and Mutter/Cogl. - I disabled a third-party GNOME Shell tiling extension after the crashes to reduce variables, but both crashes occurred before that mitigation. - A downgrade dry run back to 26.0.3-1ubuntu1 is clean and would downgrade only the six Mesa packages listed above. I have downgraded the packages currently so I can continue using teams, I will deal with the desktop flickering for the time being. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2152207 Title: Failed to lock front buffer on /dev/dri/card1: gbm_surface_lock_front_buffer failed | Failed to query buffer age, got error 3003 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2152207/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
