Open GrayBoltWolf opened 2 months ago
Does not seem to be Wayland's problem. Watch how the same thing occours on X11:
The same workaround works here too.
Supposedly this may be caused by a specific version range of libwebkitgtk, as they switched over to supporting Wayland by default, but it fails to automatically fall back to X11. This has since been fixed in the library, but some distros are still shipping older versions without the fix. When I release the next build, this might be solved, depending on the version of libwebkitgtk still being provided on Ubuntu Server 24.04 (the OS being used for the build).
In the meantime, if you try running the AppImage with WEBKIT_DISABLE_COMPOSITING_MODE=1
set as an env var, does it render okay?
In the meantime, if you try running the AppImage with
WEBKIT_DISABLE_COMPOSITING_MODE=1
set as an env var, does it render okay?
It does - I even mentioned it already under the screenshot, that the posted workaround works on X11. My main point was that the issue said it is Wayland issue, while it behaved on X11 in same way.
In the meantime, if you try running the AppImage with
WEBKIT_DISABLE_COMPOSITING_MODE=1
set as an env var, does it render okay?
rampa3's response was a bit strong, but yes, this was the workaround already posted.
Made this issue so others could find the fix as the bug is not with your app but with a gtk library.
Just noting here for others who might hit the same issue.
On Arch Linux when running in Wayland, the AppImage requires the env flag
WEBKIT_DISABLE_COMPOSITING_MODE=1
or it will be a blank screen.Without:
With:
Found from https://github.com/tauri-apps/tauri/issues/5143