I have a amd64 laptop with an nvidia dgpu and an intel igpu. I recently updated mesa to 24.1.3, the latest stable mesa. After restarting, every application that uses mesa for hw accel fails like so: >$ librewolf >MESA-LOADER: failed to open zink: /usr/lib64/dri/zink_dri.so: cannot open shared >object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri) >Segmentation fault These are my USE flags for mesa-24.1.3: >[ebuild R ] media-libs/mesa-24.1.3::gentoo USE="X (opengl) proprietary-codecs zstd -d3d9 -debug -llvm -lm-sensors -opencl -osmesa (-selinux) -test -unwind -vaapi -valgrind -vdpau -vulkan -vulkan-overlay -wayland -xa" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="sse2" LLVM_SLOT="18 -15 -16 -17" VIDEO_CARDS="intel -d3d12 (-freedreno) -lavapipe (-lima) -nouveau (-nvk) (-panfrost) -r300 -r600 -radeon -radeonsi (-v3d) (-vc4) -virgl (-vivante) -vmware -zink" 0 KiB Emerging with USE=video_cards_zink doesn't help, programs just segfault when launching. After rebuilding mesa-24.0.9, everything turned back to normal. These are the USE flags for mesa-24.0.9: >[ebuild R ] media-libs/mesa-24.0.9 USE="X gles2 (opengl) proprietary-codecs zstd -d3d9 -debug -gles1 -llvm -lm-sensors -opencl -osmesa (-selinux) -test -unwind -vaapi -valgrind -vdpau -vulkan -vulkan-overlay -wayland -xa (-zink)" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="sse2" LLVM_SLOT="-15 -16 -17" VIDEO_CARDS="intel -d3d12 (-freedreno) -lavapipe (-lima) -nouveau (-panfrost) -r300 -r600 -radeon -radeonsi (-v3d) (-vc4) -virgl (-vivante) -vmware" After realizing this, I have tried to emerge mesa-24.1.0(necessary ebuilds copied from the ::gentoo github), and it was also broken.
On my system, I need to use the following xorg.conf, else proton can't switch to my dgpu, and games proton doesn't start. I will add my xorg.conf as an attatchment, but the important part is this: >Section "ServerLayout" > Identifier "Layout0" > Screen 0 "Screen0" > Screen 0 "Screen1" > InputDevice "Keyboard0" "CoreKeyboard" > InputDevice "Mouse0" "CorePointer" >EndSection <snip> >Section "Device" > Identifier "Device0" > Driver "modesetting" > VendorName "NVIDIA Corporation" > ChipId 0x0 > ChipRev 0x0 > IRQ 0 >EndSection > >Section "Device" > Identifier "Device1" > Driver "nvidia" > VendorName "NVIDIA Corporation" > BusID "PCI:1:0:0" >EndSection <snip> >Section "Screen" > Identifier "Screen0" > Device "Device0" > Monitor "Monitor0" <snip> >EndSection <snip> >Section "Screen" > Identifier "Screen1" > Device "Device1" > Monitor "Monitor0" <snip> >EndSection With this xorg.conf, I create 2 screens, Screen0, my intel igpu, and Screen1, my nvidia dgpu, so that the X server knows about both of them and can use them both. If I disable my nvidia screen. by removing it from the ServerLayout section, >=mesa-24.1.0 works, but proton doesn't work because it can't switch to my dgpu.
Created attachment 900247 [details] xorg.conf
Created attachment 900248 [details] emerge --info
I will also add a backtrace. I got it from palemoon, because /usr/bine/librewolf is a shell script.
Created attachment 900250 [details] mesa backtrace full
Created attachment 900251 [details] mesa backtrace full unoptimized -Og
Created attachment 900252 [details] mesa backtrace full unoptimized -O0
The last -O0 backtrace seems to provide the fullest picture. Looks like strstr or memmem is called with src=NULL;
Yup, and this patch fixes the issue.
Created attachment 900253 [details, diff] fix segfault
Please make a merge request upstream.
