Provided AppImage doesn't run on Fedora 34 #3336
Labels
installation
os:linux
:type/question
Not bug, closed at will. Frequently asked ones would be collected in Logseq Forum's FAQ section.
upstream
Blocked by upstream deps
wontfix
won't fix this
Comments
|
Not a Linux expert, but maybe you could have a check with the |
Could this be related? Fedora 34 isn't that old but it seems like a reasonable explanation https://docs.appimage.org/reference/best-practices.html#binaries-compiled-on-old-enough-base-system |
|
I think .AppImage is just a package. I think it's related but not about "too old“. Maybe some library path setting in your OS is corrupted. |
|
You're correct, sorry, I misunderstood what you wanted. Though, like I said in the original issue, the executable launches fine, just not through the AppImage, which it should. `ldd -v` output |
I got your point that it's about launching from |
|
Yeah, it launches if I do |
Yes it's odd. Also wonder if any other Linux users are suffering the same. Would setup a VM to look into later. |
|
Huh, this is really weird. Running if [ -z "$APPIMAGE" ] ; then
APPIMAGE="$APPDIR/AppRun"
# not running from within an AppImage; hence using the AppRun for Exec=
fiwas somehow correcting things, but commenting it out has no effect. Here's the output from setting DEBUG output from AppImageI did the same with just running DEBUG output from AppRunWhat would you like to see from |
|
@ollien can you please update to the latest release (0.5.8) and check if the issue still exist? |
|
No dice The newly uploaded zip version works fine, though! So at least it's usable OOTB! |
|
I have the same trouble with https://github.com/logseq/logseq/tree/0.6.3 on Qubes 4.1 Debian 11 minimal template. UPDATE: the app image runs well on a full debian 11 template. When downloading the zip: |
cnrpman
added
wontfix
|
It's about basic dependency on the OS |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The provided AppImage doesn't launch on Fedora 34, due to a glibc mismatch.
I'm not sure exactly what's going on here, as I do have glibc 2.33 installed.
Interestingly, if I mount the
AppImagewith./Logseq-0.5.1.AppImage --appimage-mount, launching theLogseqexecutable from the mounted environment works fine. I was also able to make this work by manually rebuilding Logseq myself, but it's a shame that this is necessary.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Logseq should launch
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: