Satisfactory ModdingSM
Satisfactory Modding3w ago
17 replies
blouzy.1

Mod Manager Crash

Hi, I’m running into a hard crash with Satisfactory Mod Manager 3.0.3 on Linux and could use some help confirming whether this is a known issue or if there’s a workaround.

Environment:

Distro: CachyOS (Arch-based)
GPU: NVIDIA (proprietary driver)
Session: Wayland
Running the official SatisfactoryModManager_linux_amd64.AppImage

Issue:
The AppImage crashes immediately on launch with a segmentation fault. The crash happens during WebKit / EGL initialization.

Relevant output:

Cannot get default EGL display Cannot create EGL context: invalid display SIGSEGV: segmentation violation signal arrived during cgo execution github.com/wailsapp/wails/v2/internal/frontend/desktop/linux._Cfunc_SetupWebview


I’ve tried:

Forcing X11: GDK_BACKEND=x11
Unsetting Wayland: WAYLAND_DISPLAY=
Disabling compositing and GPU acceleration
Forcing Mesa / software rendering
The binary still attempts EGL initialization and segfaults instead of failing gracefully.

Observations:

This looks like Wails v2 + WebKitGTK unconditionally initializing EGL
On NVIDIA, when EGL fails, it crashes instead of falling back
Same behavior even when X11 is forced under Wayland

Questions:

Is this a known issue with the Linux AppImage?
Is there a recommended workaround (Flatpak, X11-only, specific flags)?
Has this been tested on NVIDIA + Wayland recently?
I’m happy to provide full logs or test patches if needed. Just want to know if I’m missing something obvious or if this is an upstream limitation.

Thanks in advance.
Was this page helpful?