AppImage bundles libwayland-client causing EGL failure on Fedora 44 Wayland

[MawCeron]

Environment

• VeloxDB: 0.3.1
• Fedora Linux 44
• Kernel: 7.1.9-200.fc44.x86_64
• GNOME
• Wayland
• Intel UHD Graphics 770 (Raptor Lake-S)
• x86_64

Problem

The VeloxDB AppImage does not start when launched normally:

./veloxdb_0.3.1_amd64.AppImage

It exits with:

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

Using LD_DEBUG=libs reveals the following error:

/lib64/libEGL_mesa.so.0: error: symbol lookup error: undefined symbol: wl_fixes_interface (fatal)
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

The AppImage contains its own Wayland libraries. In particular:

/tmp/.mount_veloxdlmpDcf/usr/lib/libwayland-client.so.0

while the EGL/Mesa implementation is loaded from the host system:

/lib64/libEGL_mesa.so.0

Workaround

Preloading Fedora's system libwayland-client.so.0 makes VeloxDB start successfully:

LD_PRELOAD=/usr/lib64/libwayland-client.so.0 \
./veloxdb_0.3.1_amd64.AppImage

This makes me suspect that the bundled libwayland-client.so.0 is incompatible with the system Mesa/EGL stack, or that the AppImage is incorrectly mixing bundled and host graphics libraries.

Additional dependency errors

The loader also reports errors involving the bundled GIO TLS module:

/tmp/.mount_veloxdlmpDcf/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so:
error: symbol lookup error: undefined symbol: g_module_check_init (fatal)

... undefined symbol: g_module_unload (fatal)

These may be unrelated to the EGL failure, but they appear to indicate additional dependency/library-resolution issues inside the AppImage.

Expected behavior

The AppImage should start normally on Fedora 44 using a native GNOME Wayland session without requiring LD_PRELOAD.

Workaround

LD_PRELOAD=/usr/lib64/libwayland-client.so.0 \
./veloxdb_0.3.1_amd64.AppImage

With this workaround, VeloxDB starts successfully.

I can provide the complete LD_DEBUG=libs output or additional information about the bundled libraries if needed.

[DanielJohn17]

Confirming — still present in 0.4.0, on Arch + Hyprland, not just Fedora/GNOME

Environment: VeloxDB 0.4.0 (AppImage), Arch Linux x86_64, Hyprland (Wayland), Intel Ivy Bridge HD Graphics 4000.

The 0.4.0 AppImage still bundles usr/lib/libwayland-client.so.0 (verified inside the current artifact), shadowing the host's /usr/lib/libwayland-client.so.0. WebKit's web process aborts identically every time:

(deliberate SIGABRT via raise(), captured by systemd-coredump).

Two extra data points the Fedora report doesn't cover:

1. This reproduces on Arch + Hyprland as well, so it isn't specific to Fedora/GNOME.
2. Launching the app directly isn't required — the AppImage registers org.freedesktop.FileManager1 on the session bus, so opening Nautilus D-Bus-activates VeloxDB and its WebKitWebProcess crashes the same way. Observed twice with ~100% reproduction on this machine.

The LD_PRELOAD=/usr/lib/libwayland-client.so.0 workaround looks consistent with the same root cause here (bundled libwayland vs. host Mesa libEGL_mesa.so.0), though I haven't run the live test on this box.