-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
AppImage for Linux fails to be run as glibc not found #733
Comments
v149 AppImage has the same problem with a similar error message It seems to me, ideally glibc requirement should be as low as possible to ensure maximum compatibility for many users. I am using an up to date distro, Ubuntu 22.04, which is only 1 version behind the cutting edge Ubuntu version.. And the glibc version is 3.23, and cannot be updated without destabilizng the system. Or a different AppImage creator tool can be used which compiles the proper glibc version INTO the Appimage? |
In my system AppImage does not work (only white blank screen given). If the maintainer provides the method they used to build the AppImage, I think it would be really convenient for debugging. By the way, I always appreciate the dedication put into making this app. |
if you run it on the terminal, it should output logs for you to read and paste here |
Same as #715 |
Using the latest v148 AppImage from the website.
The v145 AppImage appears to be running properly, so I have rolled back to that one.
Attempting to run the provided AppImage results in a wall of error stating the required library `GLIBC_2.38' not found. As AppImages are supposed to be prepackaged with all their dependencies inside - this seems like a bug.
System - Ubuntu 22.04
And I do have glibc-tools etc all installed, but regardless, as it's an AppImage it shouldnt fail on not having external dependencies installed which an AppImage is meant to bypass.
The text was updated successfully, but these errors were encountered: