Repository navigation
fix(appimage): use the host's C++ runtime and GPU libraries - #3
Merged
Merged
Conversation
Bulk send crashed the AppImage on Debian 13. PyInstaller bundled the build machine's libstdc++ (GLIBCXX up to 3.4.30); it wins on LD_LIBRARY_PATH, so the host's Mesa driver (libLLVM/libz3 need GLIBCXX_3.4.31+) failed to load, QtWebEngine got no OpenGL and the app died when WhatsApp Web opened. - drop libstdc++.so.6, libgcc_s.so.1 and libgbm.so.1 from the bundle - stop bundling libEGL, libGL, libGLX, libGLdispatch and libdrm These must match the host's GPU driver and are on every Linux desktop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Bulk send crashed the AppImage on Debian 13 as soon as the WhatsApp Web window opened.
PyInstaller bundles the build machine's
libstdc++.so.6. The copy in the 1.3.0 image only goes up toGLIBCXX_3.4.30, and because it comes first onLD_LIBRARY_PATH, the host's Mesa driver (radeonsi, throughlibLLVM-19/libz3, which needGLIBCXX_3.4.31+) can't load. That leaves QtWebEngine with no OpenGL (eglInitialize ... EGL_NOT_INITIALIZED,QRhiGles2: Failed to create context) and the process dies.The bundled
libgbm.so.1causes a second mismatch with the host's Mesa (did not find extension DRI_Mesa,GBM: Failed to initialize,Compositor returned null texture).Fix
In
build-appimage.sh:libstdc++.so.6,libgcc_s.so.1andlibgbm.so.1from the bundle after PyInstaller runslibEGL,libGL,libGLX,libGLdispatchandlibdrmThese have to match the host's GPU driver, and every Linux desktop has them (they're on the AppImage excludelist for that reason).
Also adds a Fixed entry under Unreleased in
CHANGELOG.md.Testing
./build-appimage.sh: the self-test and the CLI self-test pass.lddresolves every dependency oflibz3,libLLVM-19andradeonsi_dri.so(the old bundle left 3 symbol versions unresolved in each).🤖 Generated with Claude Code