Comment 19 for bug 1966108

I was wrong about it trying to use libGLX_mesa.so. I can see the same "MESA-LOADER:" message strings in libgbm, so that's presumably where they're coming from.

I think there are multiple parts to this problem:

1. If we had a newer libgbm inside the sandbox, it would instead be searching for nvidia-drm_gbm.so.

2. The nvidia-drm_gbm.so file is packaged as https://packages.ubuntu.com/jammy/libnvidia-extra-510, and snap-confine doesn't yet know to make this available within the sandbox.

3. A different set of fixes will be necessary for Wayland apps (or Chromium when we stop forcing it to use X11).

For (1), we'd need a newer Mesa in the gnome-3-38-2004 platform snap. At the moment it is just bundling Focal's Mesa, so if there are plans to do an HWE backport at some point, we might be able to benefit from that.

For (2) and (3), it'll likely require some changes to snap-confine to make the new library and data files available (probably in a few new subdirs of /var/lib/snapd/lib), and some corresponding changes to the desktop-launch script to point at these extra files.

With the Nvidia drivers now making use of some Mesa components, this basically means that there will likely be a minimum Mesa version requirement within the sandbox. It also looks like there are some open source components (e.g. https://github.com/NVIDIA/egl-wayland) that may not be appropriate to pull in from the host system as they may be built against newer library versions.