Repository navigation
v0.54.0 AppImage fails to launch on Linux — "Interpreter not found!" due to missing ld-linux-x86-64.so.2 #3103
Description
User Tekguru on Ubuntu 26.04 LTS reports that the app fails to initialize with an "Interpreter not found!" error immediately after the app-gnome-openhuman-*.scope launches. Logs shared in Discord confirm this error pattern.
Known regression — confirmed by team
Confirmed as a known bug in v0.54.0: the AppImage does not bundle ld-linux-x86-64.so.2 (the dynamic linker). The sharun launcher in the AppImage cannot find its loader on modern glibc distros, causing the crash at startup. A fix is in staging with a stable patch on the way.
Environment
Version: OpenHuman_0.54.0_amd64.AppImage
OS: Ubuntu 26.04 LTS
Team identified a one-command workaround was available pending version/distro confirmation — confirmed on 22/05/2026. Workaround was not delivered to the user. Ticket has since been pinged twice (25/05, 28/05) with no resolution provided yet.
Reported by: @tekguru_01797
Discord ticket: https://discord.com/channels/1470856511193616498/1506569602438664265
Priority: high
Attachments (1): IMG-20260521-WA0014.webp — ask support team for files
Activity
sanil-23 commentedon Jun 1, 2026
Resolved — fixed and released in v0.56.0
Root cause. The v0.54.0 AppImage was built with the
tauri-cefbundler submodule pinned atf75bc21f5, which strippedld-linux-x86-64.so.2out of the bundle. The sharun launcher needs that loader present inshared/lib/to bootstrap the dynamic binary, so on modern glibc distros (Ubuntu 26.04 here) it crashed at startup with "Interpreter not found!" before any Chromium/CEF code ran.Fix. Submodule commit
4cabccfa8("fix(appimage): keep ld-linux bundled + recurse exclude into nested dirs", merged via tauri-cef PR #16 →c90c8a330) excludes the loader from the strip pass so it stays bundled. A second guard (scripts/release/strip-appimage-graphics-libs.sh→ensure_sharun_interpreter()) now hard-fails any release build whose AppImage is missing the loader, so this can't regress silently.The submodule pin was bumped into the app via #2097 ("chore(deps): bump tauri-cef for AppImage launch fixes").
Released. v0.56.0 (2026-05-27) ships with the submodule pinned at
c90c8a330, which contains the fix. v0.54.0 was the last build cut before the bump — it pins the pre-fixf75bc21f5, which is why it's affected.Resolution for affected users (still on v0.54.0):
Closing as fixed in v0.56.0. cc @tekguru_01797 — upgrading to v0.56.0 resolves this.