You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ /path/to/any.AppImage
dlopen(): error loading libfuse.so.2
AppImages require FUSE to run.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
$ ls -al /usr/lib64/libfuse3.so*
lrwxrwxrwx 1 root root 13 2020-10-17 05:19:09 /usr/lib64/libfuse3.so -> libfuse3.so.3*
lrwxrwxrwx 1 root root 17 2020-10-17 05:19:09 /usr/lib64/libfuse3.so.3 -> libfuse3.so.3.9.1*
-rwxr-xr-x 1 root root 249552 2020-10-17 05:19:11 /usr/lib64/libfuse3.so.3.9.1*
I found nothing in the documentation mentioning version 3 of fuse, but do note that fuse-3.0.0 arrived in 2016, and the (dead) version 2 has seen no releases in more than two years. I don't understand why you still use version 2.
In searching through issues before making this post, I noticed somebody suggesting that you include (the relevant parts of) fuse in the AppImages. I heartily endorse that idea.
Reacted by Sergei Bulgakov, Evan, DrSheppard, Allan Laal, Sergey Kostrukov, Tao Hansen, Christoph Settgast, Svetlin Zarev, Mr Beedell, Roke Julian Lockhart, Pierre-Olivier Brillant and 9 more
Reacted by Simon Sobisch, Harpreet Singh, Paul, Pierre-Olivier Brillant, Ricardo FernΓ‘ndez Serrata and Abboh132
Please install libfuse2 for now; systems like CentOS 6 and 7 still need it.
Ubuntu xenial, the oldest still-supported Ubuntu LTS release, also uses it: https://packages.ubuntu.com/de/xenial/libfuse2
So we do not want to drop libfuse2 support.
As far as I know, no one has started working on (optional) support for libfuse3 so far.
Would it be feasible to link libfuse statically into the embedded AppImage runtime, and would this solve these sorts of issues? This would increase size for the sake of increasing compatibility.
You could just dlopen() and call the functions from there like it is done with libfuse2 currently. Would be easier. Also a chance to clean up the mess in the runtime, and extract all fuse-related things into some separate module.
Reacted by probonopd, 2011, Simon Sobisch and Momanyi
Would it be feasible to link libfuse statically into the embedded AppImage runtime, and would this solve these sorts of issues? This would increase size for the sake of increasing compatibility.
The entire libfuse3 dynamic library weighs in at less than 250K on my machine (I would expect an even smaller size for libfuse2). The increase in size for each AppImage (assuming you only linked in the relevant function calls) seems absolutely trivial relative to the gains in user experience. Plus it solves your problem of having to switch later. Some distributions have started to get very strict about removing apps that link to unmaintained software (Python 2.7.x or Gtk+ 2.24.x, to name two), and I expect that those distributions won't even package libfuse2 by the end of the year.
Reacted by Tao Hansen, Gun, Ricardo FernΓ‘ndez Serrata and Kornelius
Then those distributions don't have a very backward/LTS compatible mindset. In my opinion, when a new major version of a library comes along, the last major version should be carried alongside at least until even the oldest still-supported LTS releases come with the new major version, plus some extra grace period.
I don't mean to sound too argumenative here, but doesn't most LTS last about two years (people usually don't get that on many phones)? Libfuse2 has (already) died more than two years ago. Dead software doesn't have the number of eyes looking at it for potential security vulnerabilities, and distribution maintainers almost always have limited resources (and do always have demands that far exceed those resources). I can tell you that distribution packagers hate few things more that having to expend the effort required to maintain applications that demand deprecated versions of tools (and the tools often need patching themselves because other things have changed in the meantime).
Some upstream developers will simply never upgrade if they can get away with it (I know software that still requires a version from the last millennium of a common tool). Why doesn't the project upgrade? I have no idea, but can only guess some combination of arrogance, ignorance, and laziness.
Reacted by Sergey Kostrukov, haevalencia, Nils Marving, P1R0, Lucas Stauder, Screeching Bagel and Mateus Etto
Phones are clearly not our reference point. In fact, most phones become un-usable after just a few years due to them being abandoned shortly after they have been produced. I know people who are still running 10-year old desktop operating systems, ad I am typing this on a workstation that is over 10 years old and still working perfectly fine.
I can tell you that distribution packagers hate few things more that having to expend the effort required to maintain applications that demand deprecated versions of tools
And that is exactly why we need something like AppImage that embraces backward compatibility to older systems. Many distributions simply don't care and that is a problem.
Why doesn't the project upgrade? I have no idea, but can only guess some combination of arrogance, ignorance, and laziness.
Caring about users who do not want, or cannot, upgrade their operating system every couple of years.
In my personal optinion, distributions should continue to ship the -compat ("old") version of a library until it is absolutely clear that everyone (including users of distributions such as RHEL) have the new version. This would promote binary compatibility. Why don't distributions care about binary compatibility? I have no idea, but can only guess some combination of arrogance, ignorance, and laziness.
Reacted by Simon Sobisch, Gabriel Ferreira and FranTesla
So would not requiring libfuse at all, and placing the function calls needed directly in each AppImage.
Why don't distributions care about binary compatibility? I have no idea, but can only guess some combination of arrogance, ignorance, and laziness.
That seems specious to me. Distributions often have limited resources (and requests from users to add additional packages). Attempting to include deprecated libraries (especially those where the discovery of security flaws makes that more difficult) places a tremendous load on those resources. When the developer of a library moves to a new (and incompatible) version, application developers who continue to use to old library force every distribution that includes that application to do extra work. Eventually that becomes quite selfish (although libfuse2 remains recent enough that I don't mean to include applications that link to it in that description).
So would not requiring libfuse at all, and placing the function calls needed directly in each AppImage.
True, unless we still need to invoke commands like fusermount that need to be binary compatible (which I have not investigated yet).
places a tremendous load on those resources
Maybe the sweet spot would be to carry (and co-install by default) the current-1 major version, and deprecate it thereafter. Something like that. So that there is an overlap in available major library versions in all distributions (from Enterprise/LTS to bleeding edge) at any point in time. But I suspect that this kind of thinking may be alien to many distributions.
Well, in pragmatic terms, I think we should try what @TheAssassin has suggested:
If libfuse.so.2 cannot be dlopen()ed, then try to dlopen()libfuse.so.3 (and hope that nothing has changed in a breaking way).
If this doesn't work, we can always think about not requiring libfuse (and fusermount, in case we currently do) at all...
@probonopd what do you mean with using fusermount? I grepped it and didn't see it in the sources (including submodules).
I'm kinda interested in a static version of runtime that has libfuse linked into it. For my use case (high-performance computing) I really don't need all the desktop/icon/update/install stuff that come with AppImages, I just need the self-mounting squashfs. Indeed both libfuse3.so and libfuse.so are roughly 250K, so that's a size I can live with. Any obvious downsides to this?
I think squashfuse is just calling libfuse functions, and I would presume that ultimately calls fusermount yes, because at least on my distro (ubuntu 20.04) that is a setuid binary
I quickly looked into this, but the latest tagged version of squashfuse doesn't play well with libfuse 3 (apparently @TheAssassin's patches were upstreamed to Debian for the libsquashfuse0 package -- stuck on the same version then); meaning that most people likely use libfuse 2 anyways. I've created an issue in that repo to ask them to release a new version: vasi/squashfuse#50.
Actually there is a licensing issue when you statically link libfuse, because it is licensed LGPL. dlopen doesn't run into these issues so should be preferred.
Reacted by probonopd
Reacted by Ricardo FernΓ‘ndez Serrata and Gavin John
so, if as of today I want to provide an appimage that will work from, say, ubuntu 18.10 to 23.10, and does not require the user to run apt install manually, what are my options?
If you are using appimagetool, you can use --runtime-file Runtime file to use and specify the path to the runtime file you want to use, e.g., one downloaded from https://github.com/AppImage/type2-runtime/releases/tag/continuous that matches the architecture of your AppDIr.
Once @TheAssassin gives green light, we will change the default behavior to use the static runtime automatically.
(If you think we should make this easier - I think so too. Once @TheAssassin is ready for it, we will make that runtime the default in the new appimagetool, and recommend the new appimagetool instead of the one in AppImageKit.)
fuse2 is sadly unmaintained and insecure. The last released version seems to be from 2019. The other problem is that fuse2 depends on a SUID root binary. See the discussion about AppImage support removal in Fedora.
AppImage (fuse2) out-of-box support was also already removed in current Debian Stable (Trixie) release.
No typical end-user is going to manually install additional system library to get AppImages working.
Activity
probonopd commentedon Mar 4, 2021
Please install libfuse2 for now; systems like CentOS 6 and 7 still need it.
Ubuntu xenial, the oldest still-supported Ubuntu LTS release, also uses it: https://packages.ubuntu.com/de/xenial/libfuse2
So we do not want to drop libfuse2 support.
As far as I know, no one has started working on (optional) support for libfuse3 so far.
Would it be feasible to link libfuse statically into the embedded AppImage runtime, and would this solve these sorts of issues? This would increase size for the sake of increasing compatibility.
TheAssassin commentedon Mar 4, 2021
You could just
dlopen()and call the functions from there like it is done with libfuse2 currently. Would be easier. Also a chance to clean up the mess in the runtime, and extract all fuse-related things into some separate module.2011 commentedon Mar 5, 2021
The entire libfuse3 dynamic library weighs in at less than 250K on my machine (I would expect an even smaller size for libfuse2). The increase in size for each AppImage (assuming you only linked in the relevant function calls) seems absolutely trivial relative to the gains in user experience. Plus it solves your problem of having to switch later. Some distributions have started to get very strict about removing apps that link to unmaintained software (Python 2.7.x or Gtk+ 2.24.x, to name two), and I expect that those distributions won't even package libfuse2 by the end of the year.
probonopd commentedon Mar 5, 2021
Then those distributions don't have a very backward/LTS compatible mindset. In my opinion, when a new major version of a library comes along, the last major version should be carried alongside at least until even the oldest still-supported LTS releases come with the new major version, plus some extra grace period.
2011 commentedon Mar 5, 2021
I don't mean to sound too argumenative here, but doesn't most LTS last about two years (people usually don't get that on many phones)? Libfuse2 has (already) died more than two years ago. Dead software doesn't have the number of eyes looking at it for potential security vulnerabilities, and distribution maintainers almost always have limited resources (and do always have demands that far exceed those resources). I can tell you that distribution packagers hate few things more that having to expend the effort required to maintain applications that demand deprecated versions of tools (and the tools often need patching themselves because other things have changed in the meantime).
Some upstream developers will simply never upgrade if they can get away with it (I know software that still requires a version from the last millennium of a common tool). Why doesn't the project upgrade? I have no idea, but can only guess some combination of arrogance, ignorance, and laziness.
probonopd commentedon Mar 6, 2021
Phones are clearly not our reference point. In fact, most phones become un-usable after just a few years due to them being abandoned shortly after they have been produced. I know people who are still running 10-year old desktop operating systems, ad I am typing this on a workstation that is over 10 years old and still working perfectly fine.
And that is exactly why we need something like AppImage that embraces backward compatibility to older systems. Many distributions simply don't care and that is a problem.
Caring about users who do not want, or cannot, upgrade their operating system every couple of years.
In my personal optinion, distributions should continue to ship the
-compat("old") version of a library until it is absolutely clear that everyone (including users of distributions such as RHEL) have the new version. This would promote binary compatibility. Why don't distributions care about binary compatibility? I have no idea, but can only guess some combination of arrogance, ignorance, and laziness.2011 commentedon Mar 8, 2021
So would not requiring libfuse at all, and placing the function calls needed directly in each AppImage.
That seems specious to me. Distributions often have limited resources (and requests from users to add additional packages). Attempting to include deprecated libraries (especially those where the discovery of security flaws makes that more difficult) places a tremendous load on those resources. When the developer of a library moves to a new (and incompatible) version, application developers who continue to use to old library force every distribution that includes that application to do extra work. Eventually that becomes quite selfish (although libfuse2 remains recent enough that I don't mean to include applications that link to it in that description).
probonopd commentedon Mar 8, 2021
True, unless we still need to invoke commands like
fusermountthat need to be binary compatible (which I have not investigated yet).Maybe the sweet spot would be to carry (and co-install by default) the current-1 major version, and deprecate it thereafter. Something like that. So that there is an overlap in available major library versions in all distributions (from Enterprise/LTS to bleeding edge) at any point in time. But I suspect that this kind of thinking may be alien to many distributions.
Well, in pragmatic terms, I think we should try what @TheAssassin has suggested:
If
libfuse.so.2cannot bedlopen()ed, then try todlopen()libfuse.so.3(and hope that nothing has changed in a breaking way).If this doesn't work, we can always think about not requiring libfuse (and
fusermount, in case we currently do) at all...haampie commentedon Mar 23, 2021
@probonopd what do you mean with using
fusermount? I grepped it and didn't see it in the sources (including submodules).I'm kinda interested in a static version of
runtimethat has libfuse linked into it. For my use case (high-performance computing) I really don't need all the desktop/icon/update/install stuff that come with AppImages, I just need the self-mounting squashfs. Indeed both libfuse3.so and libfuse.so are roughly 250K, so that's a size I can live with. Any obvious downsides to this?haampie commentedon Mar 23, 2021
squashfuse is used, not fusermount it seems
probonopd commentedon Mar 24, 2021
Doesn't
squashfuseusefusermountinternally? Not 100% surehaampie commentedon Mar 24, 2021
I think
squashfuseis just callinglibfusefunctions, and I would presume that ultimately callsfusermountyes, because at least on my distro (ubuntu 20.04) that is a setuid binaryhaampie commentedon Mar 24, 2021
Yeah, one way to figure this out is by running
strace -fwhich dropt the setuid flag for those binaries, and then the program fails:haampie commentedon Mar 24, 2021
I quickly looked into this, but the latest tagged version of squashfuse doesn't play well with libfuse 3 (apparently @TheAssassin's patches were upstreamed to Debian for the libsquashfuse0 package -- stuck on the same version then); meaning that most people likely use libfuse 2 anyways. I've created an issue in that repo to ask them to release a new version: vasi/squashfuse#50.
haampie commentedon Mar 26, 2021
Actually there is a licensing issue when you statically link libfuse, because it is licensed LGPL.
dlopendoesn't run into these issues so should be preferred.60 remaining items
jcelerier commentedon Feb 5, 2024
so, if as of today I want to provide an appimage that will work from, say, ubuntu 18.10 to 23.10, and does not require the user to run apt install manually, what are my options?
probonopd commentedon Feb 10, 2024
That should be doable by using a statically linked AppImage runtime, e.g., https://github.com/AppImage/type2-runtime.
BobSynfig commentedon Feb 10, 2024
But people have to be aware that older (existing) AppImage will still require libfuse2 unless they are altered to use this statically linked runtime.
jcelerier commentedon Feb 11, 2024
sorry, I should have been more clear, it's not too clear for me how to instruct AppImageKit to use this new runtime ? or do I have to do it manually
probonopd commentedon Feb 12, 2024
If you are using
appimagetool, you can use--runtime-file Runtime file to useand specify the path to the runtime file you want to use, e.g., one downloaded from https://github.com/AppImage/type2-runtime/releases/tag/continuous that matches the architecture of your AppDIr.Once @TheAssassin gives green light, we will change the default behavior to use the static runtime automatically.
jcelerier commentedon Feb 13, 2024
I see. I'm not using linuxdeployqt - I do this : https://github.com/ossia/score/blob/master/ci/appimage.build.sh#L25
is the runtime the AppRun file ? The steps would be
Or are more things invlved
probonopd commentedon Feb 13, 2024
No, the runtime is not the AppRun file. And I meant
appimagetoolabove, not linuxdeployqt (I am correcting the above now). Sorry for the confusion.So instead of this
https://github.com/ossia/score/blob/53f4db8a96877aa8a49f6273c08513ef699c3f93/ci/appimage.build.sh#L22
you need to download the new one from https://github.com/AppImage/appimagetool/releases/download/continuous/appimagetool-x86_64.AppImage, and you also need to download https://github.com/AppImage/type2-runtime/releases/download/continuous/runtime-x86_64.
Then, instead of
https://github.com/ossia/score/blob/53f4db8a96877aa8a49f6273c08513ef699c3f93/ci/appimage.build.sh#L37
you need to use
(If you think we should make this easier - I think so too. Once @TheAssassin is ready for it, we will make that runtime the default in the new appimagetool, and recommend the new appimagetool instead of the one in AppImageKit.)
Hope this clears it up!
jcelerier commentedon Feb 13, 2024
thanks a lot! this is great and exactly the explanation i needed
jcelerier commentedon Feb 15, 2024
super, just in case there is a typo in the command, I think it should be
instead of
probonopd commentedon Feb 22, 2024
Of course. Correcting above. Thanks!
Use statically linked AppImage runtime.
terrancewong commentedon Nov 11, 2025
years passed, still stuck at end-of-life libfuse2.
If centos 34567, ubuntu ancient lts loves old libs, why they not just use older appimage?
AsciiWolf commentedon Nov 12, 2025
fuse2 is sadly unmaintained and insecure. The last released version seems to be from 2019. The other problem is that fuse2 depends on a SUID root binary. See the discussion about AppImage support removal in Fedora.
AppImage (fuse2) out-of-box support was also already removed in current Debian Stable (Trixie) release.
No typical end-user is going to manually install additional system library to get AppImages working.
Please, consider switching to fuse3.
probonopd commentedon Nov 12, 2025
https://github.com/AppImage/appimagetool and the runtime it uses hasn't required fuse2 since a long time.
Should the tooling you are using still result in AppImages requiring libfuse2, then please get the tooling authors to adopt the above. Thanks!
AsciiWolf commentedon Nov 12, 2025
Oops, sorry. Yeah, my tooling is based on the (probably outdated) GitHub CI. Great to hear that newer AppImages no longer require fuse2!