Comment 17 for bug 1966108

I think trying to the Mesa errors and "nvidia-drm_dri.so not found" errors are a red herring here. They indicate that Chromium is trying to use the Mesa user space GL driver, when it should be using the Nvidia user space GL driver.

As for why Firefox might work but Chromium fails, one big difference is that Firefox is a Wayland app and Chromium is an X11 app. The GLVND driver multiplexer uses different methods to pick a driver on the different window systems.

My first guess is that it is trying to dlopen() the libGLX_nvidia.so.0. If that fails, it might fall back to libGLX_mesa.so.0 and give us all these other errors. The dlopen() could fail if a library dependency is missing within the sandbox, or a library is too old.

The 510 GL driver package adds a dependency on libdrm2 and libgbm1, so perhaps it relies on something added since 20.04.

I also notice that the new driver drops files in /usr/share/egl/egl_external_platform.d/, which snap-confine and desktop-launch know nothing about. That looks like it'd be a Wayland only issue though. I don't see any reference to it in the attached strace log though.