Skip to content

.appimage not working #33

Description

@NakedHippo13

I'm on an arch based distro (Cachyos) so I downloaded .appimage variation and clicked it. But it shows a black screen for a split second then closes. It has execution permission and adding it via shelly didn't seem to help. Am I doing something wrong?
also i tried to open it via terminal then some errors popped up so i asked claude but still couldn't do anything. Heres what it says:
System:

Distro: CachyOS (Arch-based)
DE/Session: KDE Plasma, Wayland
GPU: AMD Ryzen 5700G (integrated, amdgpu driver)
Mesa: functional and working system-wide (confirmed via eglinfo — GBM, Wayland, X11, and surfaceless platforms all report AMD as vendor correctly)

Issue:
The AppImage (Linux_AppImage_Integrated.Mod.Manager.IMM._4.0.0_amd64.appimage) fails to launch. It initializes Tauri and starts the internal image server, then WebKitGTK aborts before rendering any window:

2026-07-24T11:36:36.179510355Z INFO wuwa_mod_manager_lib::image_server: Starting WWMM Image Server on 127.0.0.1:3469
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

Also present on every launch (separate, likely unrelated):

Error: in load: file "/usr/share/uim/lib/sigscheme-init.scm" not found

This crash is avoided by launching with GTK_IM_MODULE=gtk-im-context-simple, but the AppImage seems to hardcode/expect uim as a GTK input method even though it's not installed on the system — worth checking why it's referenced at all, since uim isn't a common default.

/usr/bin//xdg-mime: line 856: qtpaths: command not found

Non-fatal but noisy — xdg-mime bundled in the AppImage calls qtpaths, which isn't present.

What I've already ruled out for the EGL crash:

Not a GTK IM module issue (separate bug, worked around above)
Not GTK_IM_MODULE/QT_IM_MODULE/XMODIFIERS env vars (all unset)
Not the DMA-BUF or compositing renderer path (WEBKIT_DISABLE_DMABUF_RENDERER=1, WEBKIT_DISABLE_COMPOSITING_MODE=1 — no change)
Not Wayland vs X11 backend selection (GDK_BACKEND=x11, EGL_PLATFORM=x11 — no change)
Not software rendering fallback (LIBGL_ALWAYS_SOFTWARE=1 — no change)
Not WebKitGTK's bubblewrap sandbox (WEBKIT_DISABLE_SANDBOX=1 — no change)
Not /dev/dri permissions (user is in video/render-equivalent groups; renderD128 and card1 both accessible)
Not a system-wide Mesa/EGL problem (eglinfo succeeds cleanly on GBM/Wayland/X11/surfaceless with AMD as vendor across all)
No bundled libEGL/libGL/libgbm inside the AppImage that could conflict with system Mesa (checked via --appimage-extract)

Given eglinfo works fine standalone but the app's embedded WebKitGTK still can't get an EGL display under any backend/sandbox combination, this looks like it may be specific to how the Tauri/WebKitGTK runtime is being invoked or packaged in this AppImage build (possibly a stale/mismatched WebKitGTK version bundled or linked at build time, or an issue with how Tauri initializes its webview on Mesa/AMD specifically).

Happy to run strace or provide further logs if useful for debugging.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions