AppImage does not start on non-glibc (gnu_dev_makedev: symbol not found) and needs local-installed libfuse2 #485
Labels
Comments
lievenhey
added a commit
that referenced
this issue
Jan 23, 2024
This allows the user to run the appimage on non fuse2 systems (all moderns systems use fuse3). This is archived by using the static appimage runtime. Since linuxdeploy doesn't support changing the runtime I only use it to create the appdir directory. Then I use the original appimagetool to package the appimage using the static runtime. This should also make it possible to run the appimage on a non glibc system but I don't have access to one so I can't test it. fixes: #485
lievenhey
added a commit
that referenced
this issue
Jan 23, 2024
This allows the user to run the appimage on non fuse2 systems (all moderns systems use fuse3). This is archived by using the static appimage runtime. Since linuxdeploy doesn't support changing the runtime I only use it to create the appdir directory. Then I use the original appimagetool to package the appimage using the static runtime. This should also make it possible to run the appimage on a non glibc system but I don't have access to one so I can't test it. fixes: #485
lievenhey
added a commit
that referenced
this issue
Jan 23, 2024
This allows the user to run the appimage on non fuse2 systems (all moderns systems use fuse3). This is achieved by using the static appimage runtime. Since linuxdeploy doesn't support changing the runtime I only use it to create the appdir directory. Then I use the original appimagetool to package the appimage using the static runtime. This should also make it possible to run the appimage on a non glibc system but I don't have access to one so I can't test it. fixes: #485
lievenhey
added a commit
that referenced
this issue
Jan 23, 2024
This allows the user to run the appimage on non fuse2 systems (all moderns systems use fuse3). This is achieved by using the static appimage runtime. Since linuxdeploy doesn't support changing the runtime I only use it to create the appdir directory. Then I use the original appimagetool to package the appimage using the static runtime. This should also make it possible to run the appimage on a non glibc system but I don't have access to one so I can't test it. fixes: #485
lievenhey
added a commit
that referenced
this issue
Jan 23, 2024
This allows the user to run the appimage on non fuse2 systems (all moderns systems use fuse3). This is achieved by using the static appimage runtime. Since linuxdeploy doesn't support changing the runtime I only use it to create the appdir directory. Then I use the original appimagetool to package the appimage using the static runtime. This should also make it possible to run the appimage on a non glibc system but I don't have access to one so I can't test it. fixes: #485
lievenhey
added a commit
that referenced
this issue
Feb 6, 2024
This allows the user to run the appimage on non fuse2 systems (all moderns systems use fuse3). This is achieved by using the static appimage runtime. Since linuxdeploy doesn't support changing the runtime I only use it to create the appdir directory. Then I use the original appimagetool to package the appimage using the static runtime. This should also make it possible to run the appimage on a non glibc system but I don't have access to one so I can't test it. fixes: #485
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Starting the run-everywhere AppImage doesn't work.
To Reproduce
Try to start that on any system that has no libfuse2 (still allows to run extracted) or does not use glibc (does not start at all, error message shown in ldd).
Expected behavior
Should open.
Additional context
If I understood AppImage/AppImageKit#877 correctly then the AppImage needs to be built differently using
appimagetool --runtime-filewith the type2-runtime.The text was updated successfully, but these errors were encountered: