fix(release): strip bundled Wayland libraries from AppImage#189
Merged
su-fen merged 1 commit intoJul 21, 2026
Merged
Conversation
Member
|
感谢佬的PR,这个问题还真没仔细研究 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Linux AppImage bundles the build host's
libwayland-client,libwayland-cursor,libwayland-egl, andlibwayland-server. On hosts with newer Mesa, WebKit can load these incompatible bundled libraries and fail EGL initialization, leaving the application window blank.The v1.1.6 AppImage still contains all four libraries.
Fix
appimagetool1.9.1 and verify its published SHA-256 checksumusr/lib/**/libwayland-*.so*The
.deband.rpmartifacts and application runtime code are unchanged.Validation
AppRunandAppRun.wrapped.sigwith a temporary Tauri keybash -n scripts/release/postprocess-linux-appimage.shgit diff --checknode scripts/check-mirror.mjsCloses #128