juli/OrcaSlicer
1
1
Fork 0
mirror of https://github.com/OrcaSlicer/OrcaSlicer.git synced 2026-10-12 10:21:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Flatpak: force WebKit's shared-memory transport instead of disabling DMABUF

Browse Source 
The entrypoint exported WEBKIT_DISABLE_DMABUF_RENDERER=1 for NVIDIA. WebKit
reads that variable first and leaves the transport set empty, which turns
accelerated compositing off, so the Device tab still lagged for NVIDIA
Flatpak users, and the binary could not override it because its setenv is
non-replacing.

The runtime's WebKitGTK is vanilla, so there is no distro isNVIDIA() guard
to clear and WEBKIT_DMABUF_RENDERER_FORCE_SHM=1 alone is the right switch:
compositing stays on and only the hardware DMABUF path is skipped.
This commit is contained in:
Lam Wei Lun
2026-10-12 15:06:30 +08:00
parent 2feb5f0f9d
commit 5dba611eac
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/flatpak/entrypoint
+3 -1
View File
@@ -1,7 +1,9 @@
#!/usr/bin/env sh
# Work-around https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/754
grep -q org.freedesktop.Platform.GL.nvidia /.flatpak-info && export WEBKIT_DISABLE_DMABUF_RENDERER=1
# 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
# Work-around https://github.com/bambulab/BambuStudio/issues/3440
# Use LC_NUMERIC instead of LC_ALL to prevent decimal separator issues