#1033222 libgl1-mesa-dri: Segmentation fault with nouveau_dri.so

Package:
libgl1-mesa-dri
Source:
libgl1-mesa-dri
Description:
free implementation of the OpenGL API -- DRI modules
Submitter:
Christophe Lohr
Date:
2026-01-10 10:27:09 UTC
Severity:
normal
#1033222#5
Date:
2023-03-20 10:34:43 UTC
From:
To:
Dear Maintainer,
  Xorg is carshing with a segfault:

(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55c365ce4cf9]
(EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f00ef25af90]
(EE) 2: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (nouveau_drm_screen_create+0x4406c) [0x7f00ed75999c]
(EE) 3: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (nouveau_drm_screen_create+0x1e4c9) [0x7f00ed733df9]
(EE) 4: /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so (nouveau_drm_screen_create+0x266) [0x7f00ed715b96]
(EE) unw_get_proc_name failed: no unwind info found [-10]
../..
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)


any workaround meantime? ;-)


Best regards
Christophe

#1033222#10
Date:
2023-07-03 22:10:33 UTC
From:
To:
Hi Christophe,

Christophe Lohr wrote:

I think I've run into the same or at least a very similar issue (see
https://bugs.debian.org/1040254, reported against
xserver-xorg-video-nouveau) and my fix was (unfortunately) to switch
from xserver-xorg-video-nouveau to the non-free binary-only driver
xserver-xorg-video-nvidia with nvidia-kernel-dkms.

(Using nvidia-open-kernel-dkms instead of nvidia-kernel-dkms did not
suffice for me as it had other issues, it made X show up on only one
screen and without any xrandr or nvidia-settings capabilities.)

HTH

		Regards, Axel

#1033222#15
Date:
2024-03-27 10:09:06 UTC
From:
To:
tried to get some symbols for the given backtrace.


2:   0x00007ffff6b5999c <nouveau_screen_fini+76>: mov    0x20(%rax),%rdi
    in nouveau_pushbuf_destroy at ../src/gallium/drivers/nouveau/nouveau_screen.c:244

3:    0x00007ffff6b33df4 <nvc0_screen_destroy+260>:        call   0x7ffff6b59950 <nouveau_screen_fini>
    in nvc0_screen_destroy at ../src/gallium/drivers/nouveau/nvc0/nvc0_screen.c:740

4:    0x00007ffff6b15b93 <nouveau_drm_screen_create+611>:  call   *0x10(%rax)
    in nouveau_drm_screen_create at ../src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c:133


An internet search leads to:
https://docs.mesa3d.org/relnotes/22.3.7.html
Sam Edwards (1):
     nouveau: Fix null dereference in nouveau_pushbuf_destroy


So this looks exactly like the place of above frame 2,
and the issue might be fixed by this commit:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/4585f21de47af5e2b1a018a052ac0aaf5f1f3ac5
https://gitlab.freedesktop.org/italove/mesa/-/commit/9de997bde67df43a9e10a05f9b48419ee4cfec25
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21611


Unfortunately stable/bookworm seems to just have received mesa 22.3.6:
https://sources.debian.org/src/mesa/22.3.6-1%2Bdeb12u1/src/gallium/drivers/nouveau/nouveau_screen.c/#L244

A workaround might be to locally rebuild mesa with this patch applied.
And testing/trixie might no longer be affected with a mesa version above 22.3.7.

Kind regards,
Bernhard

#1033222#22
Date:
2025-02-09 15:14:27 UTC
From:
To:
I also had this error on bookworm-backports, a downgrade of libgl1-mesa-dri fixes it:

APT logs:
Commandline: apt install libgl1-mesa-dri=22.3.6-1+deb12u1 -t bookworm
Downgrade: libgl1-mesa-dri:amd64 (24.2.8-1~bpo12+1, 22.3.6-1+deb12u1)


[ 15148.494] (EE)
[ 15148.494] (EE) Backtrace:
[ 15148.495] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x557a1e76cf79]
[ 15148.497] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f1a4a25b050]
[ 15148.498] (EE) 2: ? (?+0x0) [0x0]
[ 15148.499] (EE) 3: /lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0xf2e) [0x7f1a49bc1eae]
[ 15148.500] (EE) 4: /lib/x86_64-linux-gnu/libgbm.so.1 (gbm_format_get_name+0x16f8) [0x7f1a49bc2678]
[ 15148.501] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 15148.501] (EE) 5: /lib/x86_64-linux-gnu/libgbm.so.1 (?+0x0) [0x7f1a49bc074c]
[ 15148.501] (EE) 6: /lib/x86_64-linux-gnu/libgbm.so.1 (gbm_create_device+0x44) [0x7f1a49bc0884]
[ 15148.502] (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x61) [0x7f1a49bf73c1]
[ 15148.504] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 15148.504] (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f1a4ae7b733]
[ 15148.505] (EE) 9: /usr/lib/xorg/Xorg (InitOutput+0x952) [0x557a1e63c582]
[ 15148.506] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x1ce) [0x557a1e5fd66e]
[ 15148.507] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) [0x7f1a4a24624a]
[ 15148.508] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x85) [0x7f1a4a246305]
[ 15148.509] (EE) 13: /usr/lib/xorg/Xorg (_start+0x21) [0x557a1e5e6b71]
[ 15148.509] (EE)
[ 15148.509] (EE) Segmentation fault at address 0x0
[ 15148.509] (EE)
Fatal server error:
[ 15148.509] (EE) Caught signal 11 (Segmentation fault). Server aborting


A similar trace can be found on https://bugs.debian.org/987722

And reading my email history at the time of installing a fresh bookworm I had crashes, same traces reported in https://bugs.debian.org/1040254
I had reported it to: https://bugs.debian.org/1027867#45

#1033222#27
Date:
2026-01-10 10:09:17 UTC
From:
To:
Es gibt eine Familienspende in Höhe von 1.850.000,00 USD von Cheng Charlie
Saephan. Bitte antworten Sie für weitere Informationen. Denken Sie daran,
Ihrer Familie und den Bedürftigen in Ihrer Umgebung Gutes zu tun.

Dies ist bereits der zweite Versuch, Sie zu erreichen. Bitte antworten Sie
für weitere Details.