-
Notifications
You must be signed in to change notification settings - Fork 82
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 GLIBC is too new (add Flatpak) #88
Comments
In my case it froze the whole OS every time I tried to click on it. |
Can you be more specific about what operating system and version you're running on? For context, Yaak does not support older OS versions, due to Tauri requiring newer lib versions. |
I'm running a CentOS Stream 9 based system, glibc 2.34
In that case, I would like to request a Flatpak package. Would you mind if I packaged Yaak for Flatpak and submitted to the Flathub repository? |
That would be great, if you'd like to take that on :) |
This issue is linked to our feedback platform. For feedback and updates, please visit this link. |
WIP packaging at https://github.com/imbev/yaak-flatpak |
I think my problem is the pc architecture because 2 of 3 the dists are for AMD, only redhat family is x64. Here is my spec:
And my glibc is checked by command
|
On linux, amd64 is synonymous with x86_64, that shouldn't be a concern.
|
What happened?
The appimage binary does not launch. This happens because my system uses an older version of GLIBC than the build system. Using an older Linux distribution for the appimage build or replacing the appimage with a Flatpak package would resolve this problem.
Version
2024.8.2
What operating system are you on?
Linux
Relevant log output
The text was updated successfully, but these errors were encountered: