Skip to main content

AppImage crashes on Fedora 44 KDE / Mesa 26.1 – EGL_BAD_PARAMETER when WebKit starts

Feature Request

Hey! I'm trying to launch the launcher (v0.3.19, AppImage) on Fedora 44 KDE (Wayland) with an RX 6700 XT and Mesa 26.1.6. The window opens, stays black, and the WebKit renderer crashes immediately.

Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

My system:

  • Fedora 44, KDE Plasma on Wayland

  • CPU/Kernel: AMD Ryzen 9 5950X, 7.1.7-200.fc44.x86_64

  • GPU: AMD RX 6700 XT

  • Mesa: 26.1.6-1.fc44

  • System-WebKitGTK: 2.52.5-1.fc44

  • GTK: 3.24.52-2.fc44

  • Launcher: ArmativeLauncher_0.3.19_amd64.appimage

Reproduction

  1. Download the AppImage, make it executable, and launch it.

  2. A window opens but remains black.

  3. Console:

[INFO] ... Setting up patcher state [INFO] Checking for updates... Could not create default EGL display: EGL_BAD_PARAMETER. Aborting... [INFO] No updates available - app is up to date  ** (ArmativeLauncher:XXXXX): WARNING **: atk-bridge: get_device_events_reply: unknown signature

Accompanied by a core dump from WebKitWebProcess (Signal: 6(ABRT)).

What I've already tried (without success)

  • sudo dnf install webkit2gtk4.1 gtk3 libappindicator-gtk3 → everything was already installed

  • WEBKIT_DISABLE_DMABUF_RENDERER=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 ...

  • WEBKIT_DISABLE_SANDBOX_THIS_IS_DANGEROUS=1 ...

  • ./ArmativeLauncher --appimage-extract && cd squashfs-root && ./AppRun

  • LD_PRELOAD=/usr/lib64/libwayland-client.so.0 ...

  • GDK_BACKEND=x11 ... and EGL_PLATFORM=surfaceless GDK_BACKEND=x11 ...

  • Force System WebKitGTK via LD_LIBRARY_PATH (AppRun hook bypassed)

The last attempt produced a fairly clear error:

ArmativeLauncher: symbol lookup error: /usr/lib64/libwebkit2gtk-4.1.so.0: undefined symbol: _ZN3JSC8JSObject19getOwnPropertyNamesEPS0_PNS_14JSGlobalObjectERNS_24PropertyNameArrayBuilderENS_22DontEnumPropertiesModeE

So: Probably an ABI mismatch. The launcher is linked to an older version of WebKitGTK than the one included with Fedora 44 (2.52.5). The system version cannot provide the symbol from JavaScriptCore.

Here is the complete console output from the first launch again:

[2026-09-23][05:36:11][armative_launcher_lib][INFO] App data directory at location: "/home/mainuser/.local/share/ArmativeLauncher"

[2026-09-23][05:36:11][armative_launcher_lib::patcher][INFO] Reading game manifests at "/home/mainuser/.local/share/ArmativeLauncher"

[2026-09-23][05:36:11][armative_launcher_lib][INFO] Setting up patcher state

[2026-09-23][05:36:11][armative_launcher_lib][INFO] Checking for updates...

Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

[2026-09-23][05:36:11][armative_launcher_lib][INFO] No updates available—app is up to date

 (ArmativeLauncher:18448): WARNING : 07:36:36.534: atk-bridge: get_device_events_reply: unknown signature

As soon as the new build is available, I’ll be happy to test it again and provide feedback.

Best, Thorsten

Posted by Thorsten Seigfried ·
1 comment

Log in to comment and vote

Comments1

  • HEAVY

    •

    Sep 24

    Additional reproduction report – CachyOS / KDE Plasma / AMD RX 9070 XT

    I can reproduce the same issue described in this report with the Armative Launcher 0.3.19 AppImage, but on CachyOS rather than Fedora.

    The launcher starts and performs its initialization/update check, but the graphical interface never renders correctly. The result is a completely grey/blank window.

    System

    • OS: CachyOS x86_64

    • Desktop: KDE Plasma 6.7.5

    • Window system: Wayland / KWin

    • Kernel: 7.2.3-1-cachyos

    • CPU: AMD Ryzen 5 7500F

    • GPU: AMD Radeon RX 9070 XT

    • Architecture: x86_64

    • Armative Launcher: 0.3.19

    • Format: AppImage

    Original launch

    Launching the AppImage normally produces:

    [2026-09-24][05:47:15][armative_launcher_lib][INFO] App data dir at location: "<user data directory>/ArmativeLauncher" [2026-09-24][05:47:15][armative_launcher_lib::patcher][INFO] Reading game manifests at "<user data directory>/ArmativeLauncher" [2026-09-24][05:47:15][armative_launcher_lib][INFO] Setting up patcher state [2026-09-24][05:47:15][armative_launcher_lib][INFO] Checking for updates... Could not create default EGL display: EGL_BAD_PARAMETER. Aborting... [2026-09-24][05:47:15][armative_launcher_lib][INFO] No updates available - app is up to date

    The application window appears, but remains completely grey/blank.

    Tests already performed

    I tested several possible Wayland/EGL/GPU-related workarounds.

    1. Force the system Wayland client library

    LD_PRELOAD=/usr/lib/libwayland-client.so.0 ./ArmativeLauncher_0.3.19_amd64.AppImage

    Result: no change.

    The exact same EGL error occurs.

    2. Force X11

    env GDK_BACKEND=x11 ./ArmativeLauncher_0.3.19_amd64.AppImage

    Result: no change.

    The same EGL error occurs and the window remains blank/grey.

    3. Force software rendering

    env LIBGL_ALWAYS_SOFTWARE=1 ./ArmativeLauncher_0.3.19_amd64.AppImage

    Result: no change.

    The same EGL error occurs.

    Application initialization

    The launcher successfully initializes its application data directory, reads its game manifests and completes its update check.

    The terminal reports:

    No updates available - app is up to date

    So the failure appears to occur specifically when the graphical/WebKit portion of the application attempts to initialize EGL.

    Reproduction

    The issue is reproducible every time:

    1. Start ArmativeLauncher_0.3.19_amd64.AppImage.

    2. The launcher performs its normal initialization.

    3. The launcher checks for updates.

    4. The terminal reports:

    Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

    1. The application window opens but is completely grey/blank.

    2. No usable UI is rendered.

    The same result occurs with the alternative launch parameters above.

    Relevant observation

    The launcher continues far enough to report:

    No updates available - app is up to date

    while the graphical/WebKit portion fails during EGL initialization.

    Since another user has reported essentially the same EGL_BAD_PARAMETER failure with Launcher 0.3.19 on KDE/Mesa, this may be related to the Linux AppImage's bundled WebKit/EGL/graphics stack rather than a machine-specific configuration problem.

    I have not modified or downgraded my system Mesa, Wayland or WebKit packages.

    If useful, I can provide additional diagnostic output such as:

    • glxinfo -B

    • eglinfo

    • wayland-info

    • relevant journalctl output

    • library dependency information

    • the list of EGL/Wayland/WebKit libraries contained in the AppImage

    • additional WebKit diagnostic output

    Hopefully this additional reproduction on CachyOS + KDE Plasma + Wayland + RX 9070 XT helps narrow down whether the problem is caused by the bundled WebKit/EGL runtime, a library version mismatch, or an incompatibility with newer Mesa/AMD environments.

    kind regards HEAVY