Is there an existing issue for this problem?

• I have searched the existing issues

Snapmaker_Orca Version

2.3.1

Operating System (OS)

Linux

OS Version

CachyOS (Arch-based)

Additional system information

• Kernel: linux-cachyos with linux-cachyos-nvidia-open 7.0.0-1 modules
• DE/WM: KDE Plasma 6 / KWin (Wayland session)
• GPU: NVIDIA GeForce RTX 2070 SUPER
• NVIDIA driver: nvidia-open 595.58.03
• OpenGL renderer (default, no Snapmaker env): NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 (native proprietary GLX — not Zink)
• Mesa EGL vendor files present: /usr/share/glvnd/egl_vendor.d/10_nvidia.json, /usr/share/glvnd/egl_vendor.d/50_mesa.json

Printer

SnapMaker U1

How to reproduce

On NVIDIA proprietary drivers (version > 555) under KDE Plasma Wayland, Snapmaker Orca crashes during slicing with VK_ERROR_MEMORY_MAP_FAILED due to the forced-Zink workaround in AppRun. Disabling that workaround (via ZINK_DISABLE_OVERRIDE=1) avoids the crash but leaves the 3D viewport completely black with no hardware-accelerated rendering path functional. This appears to be the same class of bug that was recently fixed upstream in OrcaSlicer PR OrcaSlicer#12308 ("Fixed EGL/GLX mismatch causing a blank 3D preview when running on Linux with Wayland").

Current release installed as AppImage at /opt/snapmaker-orca-appimage/snapmaker-orca-appimage.AppImage (please let me know how to retrieve the exact version string if needed — it did not print in --debug 5 output).

Steps to Reproduce

1. Launch snapmaker-orca on a KDE Plasma Wayland session with an NVIDIA GPU running driver version > 555.
2. Load any moderately complex model.
3. Trigger slicing.

Actual results

The app crashes with the following console output:

MESA: error: zink: couldn't allocate memory: heap=3 size=4194304
MESA: error: zink: couldn't allocate memory: heap=3 size=4194304
MESA: error: zink: couldn't allocate memory: heap=3 size=2097152
MESA: error: zink: couldn't allocate memory: heap=3 size=2097152
MESA: error: ZINK: vkMapMemory failed (VK_ERROR_MEMORY_MAP_FAILED)
zsh: segmentation fault (core dumped)  /usr/bin/snapmaker-orca --debug 5

This happens because AppRun detects NVIDIA driver > 555 on Wayland and sets MESA_LOADER_DRIVER_OVERRIDE=zink / GALLIUM_DRIVER=zink, forcing the app down a Zink code path that fails to map Vulkan memory on this configuration.

Expected results

Slicing completes without crashing, using hardware-accelerated rendering on the native NVIDIA OpenGL stack.

Project file & Debug log uploads

body.zip

orca-direct.log
orca-nozink.log

Checklist of files to include

• Log file
• Project file

Anything else?

I extracted the AppImage and tested every reasonable combination of environment variables. Results:

Key findings:

1. The binary in bin/snapmaker-orca links to libGL.so.1, libEGL.so.1, libGLX.so.0, and libwayland-egl.so.1 — all system libraries, no bundled Mesa.
2. glxgears runs smoothly under both native Wayland and Xwayland, so the NVIDIA GL stack is healthy.
3. glxinfo reports the native NVIDIA proprietary renderer by default — the system is not using Zink unless the AppRun explicitly forces it.
4. With Zink disabled by any method, the 3D viewport is blank regardless of which fallback GL path is forced, indicating the app's GL context initialization does not work on NVIDIA + Wayland without Zink.
5. Only software rendering fallbacks produce a usable (but impractically slow) viewport.