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

[Mario Limonciello]

> 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?

Because LM-Studio 0.4 was just released yesterday.

> For reference, these Ubuntu flavors currently seed libfuse2t64 for
older AppImage support:

So what's to stop it from being seeded again in Ubuntu desktop?  I guess
it's in universe for resolute, but it was in main at least for some
releases.

> Debian is working to remove the old fuse 2. It has already been
removed from Forky/Testing.

So maybe by next Ubuntu LTS will be the right time to remove it in
Ubuntu too.

-- 
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