AppImage v3 - EGL_BAD_PARAMETER

[ekasprzak]

Hi, can't run any v3 using AppImage on Fedora WS 41 xorg:

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

To be specific: window opens, but it's completely empty (blank).
Checked 3.1.0, 3.3.0 and latest 3.3.2.

No issue with 2.15.0.
RPM version works correctly, only AppImage is affected.

[Sparkenstein]

Let me check, could be some tauri v2 issue

[Sparkenstein]

Can you tell me more about your system? I tried on a fresh Debian VM the app worked normally for me, so I don't think it's a dependency issue.

[ekasprzak]

Let me know if there's anything more I can provide (or do some debugging).

[ekasprzak]

Just FYI, still the same with v3.4.1.
Same system as above.

There is some more output now:

 ./devtools-x_3.4.1_amd64.AppImage 

** (WebKitWebProcess:738140): WARNING **: 03:06:16.287: Error loading the injected bundle (././/lib/x86_64-linux-gnu/webkit2gtk-4.1/injected-bundle/libwebkit2gtkinjectedbundle.so): ././/lib/x86_64-linux-gnu/webkit2gtk-4.1/injected-bundle/libwebkit2gtkinjectedbundle.so: cannot open shared object file: No such file or directory

Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
** (devtools-x:738104): WARNING **: 03:06:41.157: atk-bridge: get_device_events_reply: unknown signature

[Sparkenstein]

I asked on their discord as well, most likely we can't do anything about it at the moment, I see a lot of open issues on tauri.
hopefully they will fix it in some upcoming release. I will try adding fedora on CI to build fedora apps if that's doable otherwise I can't guarantee anything

Ref: tauri-apps/tauri#11994

[ekasprzak]

Ok, thanks for the info.
Also, noticed that referenced issue is closed this as [not planned], which I don't fully understand (I planned to test every new version of devtools/appimage but with the above I don't know how to check if this was fixed upstream or not).

I will try adding fedora on CI to build fedora apps

No need, "normal" RPM on github works ;)

[Sparkenstein]

This won't be fixed upstream, most likely.
The tauri maintainers are suggesting that adding DISABLE_COMPOSITING_MODE might fix it, but it requires NO_STRIP=true.
Which will bloat binary with debug symbols. I don't want this.

If linuxdeploy (where the issue is) fixes it, then it might work out of the box someday.
But the way I see it, any new releases of devtools-x might not fix this problem anytime soon.