glvnd/egl_vendor.d contains the mesa ICD (set _EGL_VENDOR_LIBRARY_DIRS to this).drv contains the mesa drivers (set LIBGL_DRIVERS_PATH/LIBVA_DRIVERS_PATH to this).lib contains the mesa shared libraries (add to LD_LIBRARY_PATH).The Mir team are now maintaining a mesa-core20 content snap with the current mesa drivers from the archive: Care is needed to ensure that the binaries are ABI compatible, but as the binaries come from a stable archive (20.04LTS) that isn’t a problem here. And snapd has a way to share files between snaps: content interfaces. Introducing graphics-core20įundamentally, userspace graphics drivers are just files.

With Ubuntu Frame we have adopted a more flexible approach. This led to some frustration as there are a number of graphics stacks that Mir supports that were not supported by mir-kiosk. There’s no way to introduce other drivers, even if Mir supports them.Security updates to mesa require all the server and client snaps to be rebuilt and distributed and.mir-kiosk-kodi) snaps contain these drivers Until recently, we have been including the mesa drivers inside the snap as these have the least licensing issues, and cover a wide range of hardware. There’s a partial solution in snapd that, on desktop systems can make these available from the host system but among the cases where this doesn’t work is on Ubuntu Core. One of these is the need to make userspace graphics drivers available inside snap confinement. Over the past few years developing graphical snaps to run on Ubuntu Core we’ve encountered various issues. The problem with snapping userspace graphics drivers

Ubuntu graphics drivers update