Creality Print’s Flatpak would not launch from the GNOME app grid on my Fedora box. Sometimes it died immediately with a coredump; sometimes it got far enough to complain:

OpenGL lower than 2.0

Same machine runs Bambu Studio and other Flatpaks fine. Host glxinfo reported OpenGL 4.6 on the RTX 5080. The failure was specific to how Creality’s sandbox got (or did not get) graphics. Here is what was going wrong and what fixed it.

My setup

  • Fedora 43, GNOME on Wayland
  • NVIDIA GeForce RTX 5080, proprietary driver 580.159.03
  • Creality Print Flatpak io.github.crealityofficial.CrealityPrint (user install, GNOME Platform 50)
  • Matching Flatpak GL extension present: org.freedesktop.Platform.GL.nvidia-580-159-03

What the logs said

Launching from the icon produced a SIGSEGV after the in-app homepage WebView started loading: 

systemd-coredump: Process … (CrealityPrint) … dumped core.
# … frames through libwebkit2gtk / libwx_gtk3u_webview …

Forcing a WebKit workaround alone was not enough. When the app did survive long enough to init GL, it reported OpenGL < 2.0 — which is nonsense on this GPU unless the process never got a real GLX context.

Inside the Creality sandbox, with Wayland available, Flatpak often left DISPLAY unset and /tmp/.X11-unix/ empty. Force X11 and the socket appeared: 

flatpak run --command=bash --nosocket=wayland --socket=x11 \
  io.github.crealityofficial.CrealityPrint -c 'echo $DISPLAY; ls /tmp/.X11-unix/'
# DISPLAY=:0
# X0

Other Flatpaks (and org.freedesktop.Platform) got X11 without that hammer. Creality’s finish-args include wayland, x11, and fallback-x11 together; with a working Wayland socket, the X11 side for this app did not show up in practice — and Creality still wants classic GLX via X11 (wxWidgets / OpenGL canvas), not a pure Wayland GL path.

Root cause

  1. No X11 in the sandbox on GNOME Wayland → no usable GLX → “OpenGL lower than 2.0”.
  2. WebKitGTK in the homepage / device UI then segfaults on NVIDIA + Wayland/dmabuf unless you disable the dmabuf renderer.

This is the same family of NVIDIA + Wayland pain as my GNOME Videos OpenGL post, just on the Flatpak / GLX side instead of GTK GLES.

The fix (Flatpak overrides)

Apply once for the app id. GNOME’s icon uses flatpak run, so overrides apply without editing the .desktop file: 

flatpak override --user \
  --nosocket=wayland \
  --socket=x11 \
  --share=ipc \
  --device=dri \
  --env=GDK_BACKEND=x11 \
  --env=WEBKIT_DISABLE_DMABUF_RENDERER=1 \
  --env=WEBKIT_DISABLE_COMPOSITING_MODE=1 \
  io.github.crealityofficial.CrealityPrint

Confirm: 

flatpak override --user --show io.github.crealityofficial.CrealityPrint

You should see sockets=x11;!wayland; and the three environment variables. Then launch from the app grid (or gtk-launch io.github.crealityofficial.CrealityPrint).

Quick checklist

  1. flatpak info io.github.crealityofficial.CrealityPrint — note runtime and version
  2. flatpak list | grep -i nvidia — confirm GL extension matches host driver (here 580.159.03)
  3. Reproduce: icon launch → OpenGL < 2.0 and/or immediate coredump
  4. Apply the flatpak override above
  5. Relaunch; window should stay up and load the homepage without a SEGV

Related notes

  • Do not “fix” this by forcing Mesa with __GLX_VENDOR_LIBRARY_NAME=mesa on a discrete NVIDIA box — that is a different workaround for some AppImage crashes and is the wrong direction when NVIDIA Flatpak GL is already installed.
  • Leaving Wayland enabled in the sandbox is what broke GLX for this app; Creality runs under Xwayland after the override, which is fine for a slicer.
  • If you already experimented with overrides, flatpak override --user --reset io.github.crealityofficial.CrealityPrint clears them before re-applying the set above.
  • Gtk-CRITICAL spam about gtk_widget_set_size_request is noisy but unrelated; ignore it if the window stays open.

Summary

Symptom: Creality Print Flatpak — crash on launch, or “OpenGL lower than 2.0” from the GNOME icon.
Cause: No X11/GLX in the Flatpak sandbox on Wayland, plus WebKit dmabuf issues on NVIDIA.
Fix: User Flatpak overrides — force X11, GDK_BACKEND=x11, and disable WebKit dmabuf/compositing.

Hope this saves someone an evening of blaming their GPU drivers when the sandbox never got a display.