Run this in a term: Xvfb :7783 +extension GLX -nolisten tcp -nocursor -ac -screen 0 1920x1080x24 Run this in another term: DISPLAY=:7783 glxinfo | head Output should have direct rendering: Yes With x11-base/xorg-server 21.1.13-r1 this works fine with media-libs/mesa-24.1.6 or lower If you upgrade to media-libs/mesa-24.2.0 then the glxinfo command fails with Error: couldn't find RGB GLX visual or fbconfig. Xvfb outputs zero debugging info or logs, but it's basically not able to load the GLX extension. This is on a headless server. With mesa-24.1.6 the dir /usr/lib64/dri has: -rwxr-xr-x 2 root root 13411008 Aug 24 14:25 kms_swrast_dri.so -rwxr-xr-x 2 root root 13411008 Aug 24 14:25 swrast_dri.so With mesa-24.2.0 the dir /usr/lib64/dri has: lrwxrwxrwx 1 root root 14 Aug 24 14:22 kms_swrast_dri.so -> libdril_dri.so -rwxr-xr-x 1 root root 84168 Aug 24 14:22 libdril_dri.so lrwxrwxrwx 1 root root 14 Aug 24 14:22 swrast_dri.so -> libdril_dri.so I'm not sure if this is an issue with Xvfb, mesa or Gentoo. Thoughts? Reproducible: Always
Can you attach emerge --info media-libs/mesa and a > strace -e file Xvfb :7783 +extension GLX -nolisten tcp -nocursor -ac -screen 0 1920x1080x24 Running these commands works fine on multiple machines here. There were changes in mesa 24.2 that could relate though.
Created attachment 901156 [details] strace log of Xvfb with mesa-24.1.6 working
Created attachment 901157 [details] strace log of Xvfb with mesa-24.2.0 failing
Created attachment 901158 [details] emerge --info media-libs/mesa (In reply to Paul Zander from comment #1) > Can you attach emerge --info media-libs/mesa and a > > strace -e file Xvfb :7783 +extension GLX -nolisten tcp -nocursor -ac -screen 0 1920x1080x24 > > Running these commands works fine on multiple machines here. There were > changes in mesa 24.2 that could relate though. I've attached the strace logs. One with the working mesa-24.1.6 version installed and one with the failing mesa-24.2.0 installed. This is on the same system by the way. Also attached the emerge --info media-libs/mesa output
This was reported upstream to mesa and it appears it was a regression on their side: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11830