[Bug 2139352] Re: Should libfuse2 be seeded by default?

[Jeremy Bícha]

> > The situation with older AppImages is unfortunate. The official
documentation says that newer AppImages should work with libfuse3.

> Older means what in this context? I guess appimagekit?

I don't know anything more there about it than what was written on that
page. The LM Studio maintainers may be unaware of this issue.

I expect there is no chance that Ubuntu Desktop 26.04 LTS will include libfuse2t64 in the default install after it was demoted to universe years ago.
See https://launchpad.net/bugs/1965636 and https://launchpad.net/bugs/2125909

I think you're right that the old fuse 2 is likely to be available in
universe since I don't see anyone working on removing it from Ubuntu
ahead of Unstable now (although it's already been removed from Testing).

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2139352

Title:
  Should libfuse2 be seeded by default?

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  There is popular software in the ecosystem that is distributed
  *solely* as an AppImage for Linux.  An example of this is LM-Studio:

  https://lmstudio.ai/

  When trying to run it, a user is presented with the following:

  $ ./Downloads/LM-Studio-0.4.0-18-x64.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 

  If I install libfuse2t64 (which provides that) it works just fine.
  ----

  Of course; the preference would be that lm-studio packages as a Debian
  package or Snap, but the reality is there is software that doesn't do
  this.  To reduce resistance as it pertains to running this kind of
  software, I think a pragmatic response is to seed libfuse2t64 as a
  Recommends for ubuntu-meta.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2139352/+subscriptions