Skip to content

fix(appimage): drop the bundled libwayland-client so EGL can start #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Lyrex merged 1 commit into from
Jul 30, 2026
Merged

fix(appimage): drop the bundled libwayland-client so EGL can start #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions scripts/fix-appimage.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,16 @@ head -c "$offset" "$appimage" > runtime

"$appimage" --appimage-extract > /dev/null

# EGL comes from the host's Mesa, and Mesa built against wayland >= 1.23
# calls wl_display_create_queue_with_name. The libwayland-client that
# linuxdeploy bundles from the build distro predates that symbol, Mesa binds
# to the bundled copy, and EGL display creation fails with EGL_BAD_PARAMETER:
# WebKit's render process aborts and every window is blank. Same reason the
# AppImage excludelist bans exactly this library (mesa#11316); the sibling
# libwayland-* libs are fine to bundle and stay. -f, because a linuxdeploy
# with the updated excludelist will stop bundling it.
rm -f squashfs-root/usr/lib/libwayland-client.so.0

# The desktop file's real copy lives under usr/share/applications, and the
# root FrameForge.png is already a regular file, so both are safe sources.
rm squashfs-root/FrameForge.desktop squashfs-root/.DirIcon
Expand Down