Linux Appimage failing to launch

[Yi3d]

Opening the launcher using appimage produces nothing but a blank white screen for me, opening via cli shows the following:

➜  Applications ./shard-launcher-linux-x64.appimage 
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

** (shard_ui:119270): WARNING **: 18:38:38.264: atk-bridge: get_device_events_reply: unknown signature
➜  Applications 

I'm currently running Arch Linux with KDE on Wayland.

[Th0rgal]

Hi @Yi3d

Could you please let me know if using:

WEBKIT_DISABLE_DMABUF_RENDERER=1 ./shard-launcher-linux-x64.AppImage

works?

[Yi3d]

Hi @Yi3d

Could you please let me know if using:

WEBKIT_DISABLE_DMABUF_RENDERER=1 ./shard-launcher-linux-x64.AppImage

works?

Hmm no, I still get the same error in terminal with a white blank screen.

[Th0rgal]

The v0.1.7 release includes an automatic fix for the EGL issue, but since you mentioned WEBKIT_DISABLE_DMABUF_RENDERER=1 didn't help, your issue might be different.

Could you provide some more details?

• What GPU driver are you using? (nvidia proprietary or nouveau?)
• WebKitGTK version: pacman -Q webkit2gtk-4.1
• Does it work if you switch to X11/Xorg instead of Wayland?
• Can you try: WEBKIT_DISABLE_COMPOSITING_MODE=1 ./shard-launcher-linux-x64.AppImage

This will help narrow down the root cause.

[Yi3d]

The v0.1.7 release includes an automatic fix for the EGL issue, but since you mentioned WEBKIT_DISABLE_DMABUF_RENDERER=1 didn't help, your issue might be different.

Could you provide some more details?

* What GPU driver are you using? (nvidia proprietary or nouveau?)

* WebKitGTK version: `pacman -Q webkit2gtk-4.1`

* Does it work if you switch to X11/Xorg instead of Wayland?

* Can you try: `WEBKIT_DISABLE_COMPOSITING_MODE=1 ./shard-launcher-linux-x64.AppImage`

This will help narrow down the root cause.

Extremely late reply, I apologize:

• Mesa 25.3.2 on kernel driver amdgpu
• WebKitGTK version is webkit2gtk-4.1 2.50.4-1 (though isn't it packed with the appimage?)
• Using the environment variable provided here doesn't change the outcome
• I'll check x11 in a moment Didn't change anything either