So just to confirm, this happens only in a VM? The log you posted seems to show "virtio_gpu_dri.so" crashing i.e. "virtio-vga" device.

FWIW, a VM with a real card (passed through) works fine with latest mesa.

This happens in a VM and in a physical workstation , the VM is running in the threadripper machine though, it first happened in physical and then later when I updated and rebooted VM the same thing happened.

Here is log from workstation.

Ok, so it's crashing for you in 2 different scenarios (VM with virtio-vga card and physical with radeon card). That's a bit of a worry..

FWIW, I can now repro in a VM when using virtio-vga. I'm attaching 2 backtraces, but not sure how much use they'll be. Someone really needs to report to mesa devs upstream.

Here is log from workstation.

Here is log from workstation.

For the record my server is also affected by this, intel graphics card.

Same here on my laptop, Intel graphics card too.

I'm using a 4th gen Intel card and the update broke my X11 session as well (SDDM and KDE). Using Wayland still works (Sway and KDE). Some apps using OpenGL also still work (glxgears, Steam client) and some don't (certain games in my Steam library, e.g. Worms - although I'm not 100 % sure whether it is related to the mesa update).

In my case the Xorg logs look slightly different as a fallback to `i965` is attempted. This, however does not work as the required driver is only present in `mesa-amber`. Installing the old `mesa` 22.2.3 package works in my case as well. Then it loads the `crocus` driver as expected. Another workaround in my case is installing `mesa-amber` to actually use the old `i965` driver. However, some games still don't work then. (Likely in my case the `i965` driver is attempted because I have a 4th gen Intel card. If one has 5th, 6th or 7th gen than that is likely not an option so the X11 doesn't contain the fallback attempt.)

Duplicate, sorry

Happens to me in a VirtualBox VM using VMSVGA graphics controller.

FWIW, I see the same happen on a CI job (GitHub Actions with an Archlinux Docker image), running Xvfb:

_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
(EE)
(EE) Backtrace:
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 0: Xvfb (?+0x0) [0x55742afa51a4]
(EE) 1: /usr/lib/libc.so.6 (__sigaction+0x50) [0x7fca72358a00]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 2: /lib64/ld-linux-x86-64.so.2 (?+0x0) [0x7fca728ee03d]
(EE) 3: /usr/lib/libc.so.6 (_dl_catch_exception+0x7e) [0x7fca7246fe3e]
(EE) 4: /usr/lib/libc.so.6 (_dl_catch_error+0x33) [0x7fca7246fef3]
(EE) 5: /usr/lib/libc.so.6 (dlerror+0x29f) [0x7fca723a24af]
(EE) 6: /usr/lib/libc.so.6 (dlclose+0x36) [0x7fca723a2206]
(EE) 7: /usr/lib/dri/swrast_dri.so (nouveau_drm_screen_create+0x1dc8bc) [0x7fca70719f4c]
(EE) 8: /usr/lib/dri/swrast_dri.so (nouveau_drm_screen_create+0x1dbac9) [0x7fca70719159]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 9: /usr/lib/dri/swrast_dri.so (?+0x0) [0x7fca6fca3324]
(EE) 10: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x62914a) [0x7fca702cc63a]
(EE) 11: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x62909a) [0x7fca702cc58a]
(EE) 12: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x72b) [0x7fca6fca3c1b]
(EE) 13: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0xa46f) [0x7fca6fcad95f]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 14: Xvfb (?+0x0) [0x55742afb5485]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 15: Xvfb (?+0x0) [0x55742afb36f7]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 16: Xvfb (?+0x0) [0x55742aee96bc]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 17: Xvfb (?+0x0) [0x55742afd8b11]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 18: Xvfb (?+0x0) [0x55742aea0920]
(EE) 19: /usr/lib/libc.so.6 (__libc_init_first+0x90) [0x7fca72343290]
(EE) 20: /usr/lib/libc.so.6 (__libc_start_main+0x8a) [0x7fca7234334a]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 21: Xvfb (?+0x0) [0x55742aea3045]
(EE)
(EE) Segmentation fault at address 0x337
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)

Looks like this might be happening in environments where only software rendering is available? Possibly related upstream report and fix:

- https://gitlab.freedesktop.org/mesa/mesa/-/issues/7819
- https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20145/diffs?commit_id=b3d1ae19f2f4d93cf0a5f45a598149ac4e8e05aa

Me and two other users have already stated problems with Intel cards. So I don't think this is only about software rendering.

Looks like some promising changes have landed in staging, thanks for that. I'll test them once https://archlinux.org/todo/spirv-20222-glslang-11120-shaderc-20223-rebuild has been completed.

Can confirm. I noticed it when rebooting and had issues with SDDM (uses Xorg) not displaying. Switching to GDM works fine, since it uses Wayland. Every Wayland session works fine. Initially i thought there was simply something wrong with my sddm installation, but reinstalling it didn't fix it. The only testing packages i am using are mesa ones... Intel igpu (Core i5 11500).

I confirm the issue, on my own laptop (2017 8th gen intel kaby lake r / intel uhd graphics 620 gpu, xfce 4.16).

Fails with 22.3.0-1 (testing/mesa), downgrading to 22.2.3-1 (extra/mesa) works, as well as mesa-amber.

There's a similar thread on linux.debian.bugs.dist:

https://groups.google.com/g/linux.debian.bugs.dist/c/jRGHe9F2BWA

However, unlike a proposed solution, clearing /etc/X11/xorg.conf.d/* and /usr/share/X11/xorg.conf.d/* doesn't fix it.


Xorg.0.log output:
---

X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
Current Operating System: Linux 6.0.11-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 02 Dec 2022 17:25:31 +0000 x86_64
Current version of pixman: 0.42.2
Using system config directory "/usr/share/X11/xorg.conf.d"

xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)
(EE)
(EE) Backtrace:
(EE) 0: /usr/lib/Xorg (dri3_send_open_reply+0xdd) [0x55ab2a06abad]
(EE) 1: /usr/lib/libc.so.6 (__sigaction+0x50) [0x7fb36c650a00]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 2: /lib64/ld-linux-x86-64.so.2 (?+0x0) [0x7fb36cc3003d]
(EE) 3: /usr/lib/libc.so.6 (_dl_catch_exception+0x7e) [0x7fb36c767e3e]
(EE) 4: /usr/lib/libc.so.6 (_dl_catch_error+0x33) [0x7fb36c767ef3]
(EE) 5: /usr/lib/libc.so.6 (dlerror+0x29f) [0x7fb36c69a4af]
(EE) 6: /usr/lib/libc.so.6 (dlclose+0x36) [0x7fb36c69a206]
(EE) 7: /usr/lib/dri/swrast_dri.so (nouveau_drm_screen_create+0x1dc8bc) [0x7fb368f1ef4c]
(EE) 8: /usr/lib/dri/swrast_dri.so (nouveau_drm_screen_create+0x1dbac9) [0x7fb368f1e159]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 9: /usr/lib/dri/swrast_dri.so (?+0x0) [0x7fb3684a8324]
(EE) 10: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x62914a) [0x7fb368ad163a]
(EE) 11: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x62909a) [0x7fb368ad158a]
(EE) 12: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x72b) [0x7fb3684a8c1b]
(EE) 13: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0xa46f) [0x7fb3684b295f]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 14: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fb36bcf6a27]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 15: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fb36bcef48f]
(EE) 16: /usr/lib/Xorg (_CallCallbacks+0x3c) [0x55ab29f8951c]
(EE) 17: /usr/lib/Xorg (xf86DRI2Enabled+0x27d7) [0x55ab2a072667]
(EE) 18: /usr/lib/Xorg (InitExtensions+0x89) [0x55ab29f56f29]
(EE) 19: /usr/lib/Xorg (SProcXkbDispatch+0x1809) [0x55ab29f4a054]
(EE) 20: /usr/lib/libc.so.6 (__libc_init_first+0x90) [0x7fb36c63b290]
(EE) 21: /usr/lib/libc.so.6 (__libc_start_main+0x8a) [0x7fb36c63b34a]
(EE) 22: /usr/lib/Xorg (_start+0x25) [0x55ab29f4b475]
(EE)
(EE) Segmentation fault at address 0x337
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

mesa 22.3.1-1 doesn't crash for me anymore (VirtualBox VM using VMSVGA graphics controller).

mesa 22.3.1-1 seems to fix this, both my threadripper workstation and Virtual machine (QEMU) is now fully updated and has no issues with mesa.

fixed for me aswell.

Fixed for me with 22.3.1-1 too.

Fixed.