AppImage shows only white screen since v0.2.2 (EGL_BAD_PARAMETER)

[steepdawn974]

Bug description

Starting with the v0.2.2 AppImage the application window never finishes loading – only a blank white screen is shown.
Console prints:

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

Downgrading to the v0.2.1 AppImage works fine.

Steps to reproduce

1. Download keeper-desktop_0.2.2_amd64.AppImage
2. chmod +x keeper-desktop_0.2.2_amd64.AppImage
3. ./keeper-desktop_0.2.2_amd64.AppImage
4. Window opens → stays white forever
   (same result on both Wayland and X11 sessions)

Environment

• OS: Arch Linux (kernel 6.11)
• Mesa: 24.2.3
• libwebkit2gtk-4.0-37 (system): 2.44
• GPU: Intel

Root cause

The v0.2.2 AppImage bundles its own copy of libwebkit2gtk-4.0-37 that was built against Ubuntu 22.04's older EGL/Mesa headers.
When the runtime web-process tries to create an EGL context it receives EGL_BAD_PARAMETER and aborts, leaving the front-end window empty.

Possible Work-around (suggested by AI; not verified!)

Delete the bundled library so the AppImage falls back to the system's up-to-date webkit:

sudo mount -o loop keeper-desktop_0.2.2_amd64.AppImage /mnt
sudo rm /mnt/usr/lib/libwebkit2gtk-4.0-37.so*
sudo umount /mnt

Suggested fix (suggested by AI; not verified!)

Do not ship libwebkit2gtk-4.0-37 inside the AppImage (or rebuild it on an Ubuntu ≥24.04 runner with current Mesa/EGL) so the host driver stack is used.

Additional context

Issue identical to the EGL regression seen in other Tauri-based AppImages --> https://github.com/music-assistant/companion/issues/57
Affects both Wayland and X11 sessions.

[abradshaw]

I also have this problem on Fedora44

[abradshaw]

I have more info after I rebuilt it

The pre-built packages (AppImage and RPM) for keeper-desktop v0.2.4 all failed to run on Fedora 44 because they bundle or depend on libwebkit2gtk-4.0, which Fedora 44 dropped entirely in favour of libwebkit2gtk-4.1. The app is built
with Tauri, and the released version uses Tauri v1 which targets webkit2gtk 4.0

I migrated the app from Tauri v1 to Tauri v2, which supports webkit2gtk 4.1. Changes made:

• Updated Cargo.toml to tauri/tauri-build v2, added tauri-plugin-shell
• Replaced tauri::api::process::Command with std::process::Command for the HWI sidecar binary
• Added use tauri::Emitter imports where needed (emit_all → emit)
• Rewrote tauri.conf.json and tauri.release.conf.json in the v2 schema format
• Created capabilities/default.json (v2's replacement for the allowlist)
• Updated npm packages (@tauri-apps/api and @tauri-apps/cli 1→2) and frontend import paths

The issue now is that the app launches and renders correctly, but can't function because both of the project's relay servers (keeper-channel.herokuapp.com and its dev equivalent) have been deleted from Heroku. The relay is a Socket.IO server that acts as a
bridge between the desktop app and the Bitcoin Keeper mobile app when pairing a hardware wallet. Without it, the desktop app can't communicate with the mobile app at all. The relay code is not publicly available in their GitHub repos.