Blank screen on Ubuntu 26.04

0.1.5: I'm now able to open the app normally without the terminal on Fedora 44.

However, if I run it via terminal, I still get errors:

/usr/bin/xdg-mime: line 885: qtpaths: command not found 
[any] backend config: default (server-packaged network) 
Gtk-Message: 22:39:41.783: Failed to load module "colorreload-gtk-module" 
Gtk-Message: 22:39:41.783: Failed to load module "window-decorations-gtk-module"

I did notice some visual issues inside the app which might be related to those errors (let me know if a separate bug report is preferred):

• Some buttons have no icons, eg: "New space", "New Favorites folder", "Close tab":

  

• The "Window" menu is empty:

  

I've applied a fix -- it should come with the next update!

I've got a similar issue running Anytwo 0.1.4 on Fedora 44, X11, kernel 7.2.7.

Steps:

• Left click on the appimage.
• App opens but there's only a blank screen:
  

• A crash notice appears:

  /tmp/.mount_AnytwoiPgbfJ/usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitWebProcess has encountered a fatal error and was closed.

Running the appimage from the terminal gives the following output:
[any] backend config: default (server-packaged network)

Gtk-Message: 17:10:46.875: Failed to load module "colorreload-gtk-module"

Gtk-Message: 17:10:46.875: Failed to load module "window-decorations-gtk-module"

Could not create default EGL display: EGL_BAD_PARAMETER. Aborting…


I've got some success running the app via terminal with LD_PRELOAD=/usr/lib64/libwayland-client.so.0.

This way, I was able to open the app correctly and create an account. After a while I got a system freeze though.

Thank you all for detailed logs!

my fault, i was a little bit lazy and was using pure browser version for some period and didn't test it properly... We will give it some love and make sure to keep it active on our desktops on a daily basis.

Same step...
Good catch for Wayland files by the way!
I simply delete them (an install libwayland-server0) and it worked! Then I updated it, and back to square one...

The attached script did the trick, you just need to run it after clicking on update button (close the blank window, run the script and open again). It rebuilds the AppImage, so you need appimagetool

#!/usr/bin/env bash
set -euo pipefail

# Usage: patch.sh [path/to/any.appimage]
# no need to pass path if AppImage is on your PATH

# Locate any.appimage from PATH or first argument
APPIMAGE="${1:-$(which any.appimage 2>/dev/null || which any.AppImage 2>/dev/null || true)}"

if [[ -z "$APPIMAGE" || ! -f "$APPIMAGE" ]]; then
    echo "Error: any.appimage not found on PATH or provided as an argument." >&2
    echo "Usage: $0 [path/to/any.appimage]" >&2
    exit 1
fi

# Resolve to absolute path before changing directory
APPIMAGE="$(readlink -f "$APPIMAGE")"

echo "==> Patching: $APPIMAGE"

# Create temporary working directory in /tmp and ensure cleanup on exit
TMPDIR="$(mktemp -d /tmp/any-patch.XXXXXX)"
trap 'rm -rf "$TMPDIR"' EXIT

cd "$TMPDIR"

# 1. Unpack
echo "==> Extracting to $TMPDIR..."
"$APPIMAGE" --appimage-extract > /dev/null

# 2. Remove conflicting bundled Wayland libraries
echo "==> Removing bundled Wayland libraries..."
find squashfs-root/usr/lib -name "libwayland*" -delete

# 3. Prevent host GIO/GVFS symbol mismatch (optional)
sed -i '2i export GIO_MODULE_DIR=""' squashfs-root/AppRun

# 4. Rebuild with appimagetool and replace original binary
echo "==> Rebuilding AppImage..."
export ARCH="$(uname -m)"
appimagetool squashfs-root any-patched.AppImage > /dev/null
mv -f any-patched.AppImage "$APPIMAGE"
chmod +x "$APPIMAGE"

echo "==> Done! Replaced $APPIMAGE with the patched build."

It seems the same bug impacts update. :|

- Anytwo detects a new version available (0.1.2)
- Downloads it, and offers option to update, but...
- When I click the "Update" button it somehow reverts the workaround, and I'm back to the blank window again and get new error log messages:

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

~/Projects/anytwo ❯ Gtk-Message: 16:22:56.547: Failed to load module "canberra-gtk-module"

Gtk-Message: 16:22:56.548: Failed to load module "canberra-gtk-module"

[any] backend config: default (server-packaged network)

Bug Report Complement

1. Symptoms & Terminal Logs

When running Anytwo AppImage, the window frame and menu bar ("Edit", "Window", "Help", "Debug") render, but the webview area remains completely blank / empty:

At the same time, the terminal outputs the following log and aborts:

/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_variant_builder_init_static
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
[any] backend config: default (server-packaged network)
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_variant_builder_init_static
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

Note: it seems the GVFS lines are non-fatal warnings from GLib scanning host GIO modules. The fatal abort is Could not create default EGL display: EGL_BAD_PARAMETER.

2. What We Tried That Did NOT Work

1. Disabling DMA-BUF rendering in WebKitGTK:

   WEBKIT_DISABLE_DMABUF_RENDERER=1 ./any.appimage
   

   Result: Still aborted with Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

2. Disabling WebKitGTK compositing mode (forcing software rendering):

   WEBKIT_DISABLE_COMPOSITING_MODE=1 ./any.appimage
   

   Result: Still aborted with Could not create default EGL display: EGL_BAD_PARAMETER. Aborting... (the failure happens during early PlatformDisplay initialization before compositing mode takes effect).

3. Changing GDK backend from X11 to Wayland: Editing squashfs-root/apprun-hooks/linuxdeploy-plugin-gtk.sh to remove export GDK_BACKEND=x11 and running:

   GDK_BACKEND=wayland ./squashfs-root/AppRun
   

   Result: Added Fontconfig warning: using without calling FcInit() and still aborted with Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

3. Exactly What Worked

The issue was resolved by removing the AppImage's bundled Wayland libraries and pointing GIO away from host modules:

# 1. Extract the AppImage
./any.appimage --appimage-extract

# 2. Rename/remove the bundled Wayland libraries in squashfs-root/usr/lib
# (This forces the app to load the host system's Wayland libraries instead)
mv squashfs-root/usr/lib/libwayland-client.so.0 squashfs-root/usr/lib/libwayland-client.so.0.bak
mv squashfs-root/usr/lib/libwayland-egl.so.1 squashfs-root/usr/lib/libwayland-egl.so.1.bak
mv squashfs-root/usr/lib/libwayland-cursor.so.0 squashfs-root/usr/lib/libwayland-cursor.so.0.bak
mv squashfs-root/usr/lib/libwayland-server.so.0 squashfs-root/usr/lib/libwayland-server.so.0.bak

# 3. Launch with GIO_MODULE_DIR cleared (silences the GVFS warning, optional)
GIO_MODULE_DIR="" ./squashfs-root/AppRun

Output on success:

[any] backend config: default (server-packaged network)

The window created its display cleanly, the initial UI content loaded, and the blank screen / crash was resolved:

4. OS and Environment Details

What was your error? Something related to "default EGL display"? I've been struggling with this since yesterday (but since I'm on Windows, I tried using WSL and then a real VM... but still without success)