-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[App] Beta 1.2.1 - Ubuntu - Error launching the AppImage #402
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.
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
Comments
Dylan-86
added a commit
to Dylan-86/void
that referenced
this issue
Apr 15, 2025
Thanks, this is super helpful! |
This was referenced Apr 18, 2025
Same error on
|
Same error on |
Same with
I'm on arch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just tried the new appImage for Ubuntu
./Void-1.2.0.25104.glibc2.29-x86_64.AppImage
When I run it, I get the following output:
The warning from sed is not a blocker, but the second line is — the app doesn't start.
Investigation
Let's go:
I extracted the AppImage using:
./Void-1.2.0.25104.glibc2.29-x86_64.AppImage --appimage-extract
Then checked the contents:
the binary exist inside the extracted AppImage
./usr/share/void/void
And if I run it manually:
…it works as expected.
Conclusion
It looks like the AppRun script is trying to launch the binary using an absolute path:
exec /usr/share/void/void
Please consider changing the AppRun script to use a relative path instead, like:
exec ./usr/share/void/void "$@"
ok
exec "$(dirname "$0")/usr/share/void/void" "$@"
Dylan
The text was updated successfully, but these errors were encountered: