-
Notifications
You must be signed in to change notification settings - Fork 70
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
Appimages won't work with fuse3 unless fusermount is symlinked to fusermount3 #278
Comments
Need to backport the workaround for |
probonopd
added a commit
that referenced
this issue
Apr 14, 2024
probonopd
added a commit
that referenced
this issue
Apr 14, 2024
Thank you, it works now! |
Thanks for bringing this up and for testing. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context: ivan-hc/AM#387
Archlinux has separate fuse2 and fuse3 packages, and they never get symlinked, so if only fuse3 is installed and you try to use an appimage that can work with fuse3 it won't actually work because it will give a missing fusermount error.
Doing an
ln -s /usr/bin/fusermount3 /usr/bin/fusermount
fixes the issue. But I don't know if this is an intended behavior of the distro or the fuse packages themselves. And also shouldn't the appimage itself try to use fusermount3 anyway?It seems like debian does symlink fusermount to fusermount3.
The text was updated successfully, but these errors were encountered: