[Bug]: Tauri AppImage segfaults on Ubuntu 24.04 + Wayland

[bcdady]

App Variant

Tauri

Operating System & Version

Ubuntu 24.04 (Linux), Wayland session

Issue Summary

The Tauri AppImage (v0.16.0, x64) immediately segfaults on launch. The documented workaround (WEBKIT_DISABLE_DMABUF_RENDERER=1) does not help, nor does forcing X11 via GDK_BACKEND=x11.

Steps to Reproduce

1. Download CodeNomad-Tauri-linux-x64-0.16.0.AppImage from releases
2. chmod +x CodeNomad-Tauri-linux-x64-0.16.0.AppImage
3. Run it:

$ ./CodeNomad-Tauri-linux-x64-0.16.0.AppImage
Segmentation fault (core dumped)

4. Try documented workaround:

$ WEBKIT_DISABLE_DMABUF_RENDERER=1 ./CodeNomad-Tauri-linux-x64-0.16.0.AppImage
Segmentation fault (core dumped)

5. Try forcing X11 backend:

$ GDK_BACKEND=x11 WEBKIT_DISABLE_DMABUF_RENDERER=1 ./CodeNomad-Tauri-linux-x64-0.16.0.AppImage
Segmentation fault (core dumped)

All three produce exit code 139.

Expected Behavior

The Tauri desktop app should launch, or at minimum produce a meaningful error message instead of a segfault.

Logs & Screenshots

No output is produced before the segfault — just Segmentation fault (core dumped).

Additional Context

• Session type: Wayland (echo $XDG_SESSION_TYPE → wayland)
• libwebkit2gtk-4.1-0 is installed
• The server CLI mode (npx @neuralnomads/codenomad) works fine on the same system
• The README notes Tauri is "experimental"

Co-Authored-By: Oz oz-agent@warp.dev

[shantur]

Hey @bcdady

Thanks for trying CodeNomad
Any more logs that can be found?

[itrs]

same here:

❯ ~/Apps/CodeNomad-Tauri-linux-x64-0.16.0.AppImage --no-sandbox --disable-gpu
[1] 2895011 segmentation fault (core dumped) ~/Apps/CodeNomad-Tauri-linux-x64-0.16.0.AppImage --no-sandbox --disable-gpu

[shantur]

@CodeNomadBot

Can you check why it could be happening

[codenomadbot]

I checked the Tauri Linux startup/build path.

What I understand the request to be: investigate why CodeNomad-Tauri-linux-x64-0.16.0.AppImage can segfault immediately on Ubuntu 24.04 Wayland, even with WEBKIT_DISABLE_DMABUF_RENDERER=1 and GDK_BACKEND=x11. I’m assuming we are looking for likely cause/next diagnostics rather than changing code yet.

Findings:

• The crash is very likely happening in the native Tauri/Wry/WebKitGTK startup path before our app code gets far enough to emit logs. The main window is created from tauri.conf.json with loading.html, and the app only starts the bundled CLI later in setup, on a background thread. A silent exit 139 before any output points more to GTK/WebKit/graphics/AppImage runtime than to the CodeNomad server process.
• The Linux bundle is built on ubuntu-24.04 with libwebkit2gtk-4.1-dev, libsoup-3.0-dev, GTK3, and Tauri CLI 2.9.4. Runtime requires the host WebKitGTK 4.1 stack, which the reporter has installed.
• The documented workaround only targets a known WebKitGTK DMA-BUF/GBM renderer issue, commonly seen with Wayland/NVIDIA. Since it still segfaults with WEBKIT_DISABLE_DMABUF_RENDERER=1, this is probably not that exact issue, or there is another graphics/driver crash below WebKitGTK. Also, --disable-gpu is a Chromium/Electron-style flag and is unlikely to affect Tauri/WebKitGTK.
• GDK_BACKEND=x11 alone may not avoid a WebKit compositor/driver crash if the system still loads the same GL/EGL stack, or if XWayland/driver interaction is what crashes.
• I did not find a CodeNomad Linux-only startup hook that obviously explains an immediate segfault. The only Linux-specific Rust code is for TLS handling on remote windows and should not run during the initial main-window launch.

Useful next diagnostics from an affected machine:

# Confirm whether the raw binary behaves differently from AppImage runtime
unzip CodeNomad-Tauri-linux-x64-0.16.0.zip -d codenomad-tauri-bin
./codenomad-tauri-bin/codenomad-tauri

# Capture native crash location
coredumpctl info CodeNomad
coredumpctl gdb CodeNomad --batch -ex 'thread apply all bt full'

# Try forcing software GL; this helps distinguish WebKit/driver crash from app crash
LIBGL_ALWAYS_SOFTWARE=1 WEBKIT_DISABLE_DMABUF_RENDERER=1 ./CodeNomad-Tauri-linux-x64-0.16.0.AppImage

# Get dynamic linker / WebKit-related hints if it fails before a core is useful
G_MESSAGES_DEBUG=all RUST_BACKTRACE=full ./CodeNomad-Tauri-linux-x64-0.16.0.AppImage

Most likely root cause at this point: host WebKitGTK/GTK graphics initialization is crashing under Ubuntu 24.04 Wayland for this AppImage, not the bundled CodeNomad CLI. The highest-value evidence would be the coredumpctl gdb backtrace; if it lands in libwebkit2gtk, libjavascriptcoregtk, Mesa/NVIDIA/GL/EGL, or GTK/GDK, that confirms the native runtime path. If the raw zip binary launches while AppImage crashes, then the AppImage runtime/bundling layer is implicated instead.

--
Yours,
CodeNomadBot