Flatpak: drop the WebKit NVIDIA export; the binary owns the workaround

/proc/driver/nvidia/version is readable inside the Flatpak sandbox, so the
binary's NVIDIA branch already sets WEBKIT_DMABUF_RENDERER_FORCE_SHM with
the correct runtime gate and the entrypoint's own export is redundant.

Verified with:
  flatpak run --command=cat com.orcaslicer.OrcaSlicer /proc/driver/nvidia/version
which prints the NVRM version (driver 615.71.09) from inside the sandbox.
This commit is contained in:
Lam Wei Lun
2026-10-12 15:49:58 +08:00
parent 5dba611eac
commit 2b736dd268
+2 -4
View File
@@ -1,9 +1,7 @@
#!/usr/bin/env sh
# Work-around https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/754
# The runtime's WebKitGTK cannot back its DMABUF renderer on the NVIDIA driver.
# WEBKIT_DISABLE_DMABUF_RENDERER is read first and would leave compositing off.
grep -q org.freedesktop.Platform.GL.nvidia /.flatpak-info && export WEBKIT_DMABUF_RENDERER_FORCE_SHM=1
# WebKit's NVIDIA DMABUF workaround (gnome-build-meta#754) is applied by the
# binary itself, gated on the runtime WebKitGTK version (src/OrcaSlicer.cpp).
# Work-around https://github.com/bambulab/BambuStudio/issues/3440
# Use LC_NUMERIC instead of LC_ALL to prevent decimal separator issues