possibly, but there seems to be more damage with regards to the gpu snap and env. I am getting bug reports all over. Most notably Freecad isn’t functional at all. I fixed the LD_LIBRARY_PATH problem just by adding it to my launcher.
Can’t be the gpu wrapper ? In addition to ‘mount namespace’ errors happening everywhere?
#!/bin/bash
set -euo pipefail
# The second content element is mounted at "${content_target}-2"
COMPONENT_PATH="$( cd -- "$(dirname "$0")"/.. ; pwd -P )-2"
# Use the component mangler to bootstrap the environment
if [ -f ${COMPONENT_PATH}/@COMPONENT_SENTINEL@ ]; then
. ${COMPONENT_PATH}/@COMPONENT_MANGLER@
fi
SELF_BASE="$( cd -- "$(dirname "$0")/.." ; pwd -P )"
SELF=${SELF_BASE}/usr
ARCH_TRIPLETS=( @ARCH_TRIPLETS@ )
# VDPAU_DRIVER_PATH only supports a single path, rely on LD_LIBRARY_PATH instead
for arch in ${ARCH_TRIPLETS[@]}; do
GBM_BACKENDS_PATH=${GBM_BACKENDS_PATH:+$GBM_BACKENDS_PATH:}${SELF}/lib/${arch}/gbm
LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}${SELF}/lib/${arch}:${SELF}/lib/${arch}/dri:${SELF}/lib/${arch}/vdpau
LIBVA_DRIVERS_PATH=${LIBVA_DRIVERS_PATH:+$LIBVA_DRIVERS_PATH:}${SELF}/lib/${arch}/dri
This file has been truncated. show original
mr_cal
July 7, 2026, 12:18pm
23
Ok, I think this is something that needs to be fixed, so I’ve created an issue for it: Snapcraft 9 incorrectly sets LD_LIBRARY_PATH and QT_LIBRARY_PATH in the extensions · Issue #6327 · canonical/snapcraft · GitHub .
I’m not sure about the namespace errors mentioned above at install time or how it relates to the gpu wrapper. @saviq - have you seen these?
Saviq
July 7, 2026, 2:57pm
24
Not seen those, no, and they don’t seem related to Mesa, at least from those logs.