Главная » Ошибки » Bug #1965636 “libfuse2 no longer included in jammy, required for

Bug #1965636 “libfuse2 no longer included in jammy, required for

Bug Description

Attempting to run an AppImage in Xubuntu 22.04 displays the following error:

$ ./cryptomator-1.6.5-x86_64.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 wiki/FUSEAppImageKit/com/AppImage//github.https:/
for more information

Simply installing libfuse2 resolves this issue. Some flavors seem to still include it. I noticed that today’s Ubuntu MATE daily still does. Ubuntu and Xubuntu do not.

Ubuntu: arm64.manifestjammy-desktop-live/current/com/daily-ubuntu./cdimage.https:/
Xubuntu: amd64.manifestjammy-desktop-current/daily-live/com/xubuntu/ubuntu./cdimage.https:/
Ubuntu MATE: amd64.manifestjammy-desktop-live/current/mate/daily-com/ubuntu-ubuntu./cdimage.https:/

Tags:

jammy

Erich Eickmeyer  (eeickmeyer)

on 2022-03-19

Changed in ubuntustudio-meta (Ubuntu):
status: New → Fix Committed

Sean Davis (bluesabre)

on 2022-03-19

Changed in xubuntu-meta (Ubuntu):
status: New → Fix Committed

Revision history for this message

Launchpad Janitor (janitor)
wrote
on 2022-03-19:
#1

This bug was fixed in the package xubuntu-meta – 2.240

—————
xubuntu-meta (2.240) jammy; urgency=medium

  * Refreshed dependencies
  * Added language-selector-common to core, desktop
  * Added libfuse2 to core-recommends, desktop-recommends (LP: #1965636)

 — Sean Davis

—————
xubuntu-meta (2.240) jammy; urgency=medium

* Refreshed dependencies
* Added language-selector-common to core, desktop
* Added libfuse2 to core-recommends, desktop-recommends (LP: #1965636)

— Sean Davis Sat, 19 Mar 2022 15:39:38 -0400

Changed in xubuntu-meta (Ubuntu):
status: Fix Committed → Fix Released

Erich Eickmeyer  (eeickmeyer)

on 2022-03-19

Changed in ubuntustudio-meta (Ubuntu):
status: Fix Committed → Fix Released

Rik Mills (rikmills)

on 2022-03-21

Changed in kubuntu-meta (Ubuntu):
status: New → Fix Committed

Revision history for this message

Launchpad Janitor (janitor)
wrote
on 2022-03-21:
#2

This bug was fixed in the package kubuntu-meta – 1.418

—————
kubuntu-meta (1.418) jammy; urgency=medium

  * Refreshed dependencies
  * Added libfuse2 to desktop-recommends (LP: #1965636)

 — Rik Mills

—————
kubuntu-meta (1.418) jammy; urgency=medium

* Refreshed dependencies
* Added libfuse2 to desktop-recommends (LP: #1965636)

— Rik Mills Mon, 21 Mar 2022 07:24:00 +0000

Changed in kubuntu-meta (Ubuntu):
status: Fix Committed → Fix Released

Revision history for this message

probono (probono)
wrote
on 2022-03-27:
#3

Apparently this affects most if not all flavors of Ubuntu. Especially the default flavor.

The AppImage format for distributing applications is centered around the idea that a user can boot the Ubuntu Live ISO, download an application in AppImage format, make it executable, and run it without having to install anything.

Not having libfuse2 and fusermount on the Live ISO breaks this for all existing AppImages out there.

AppImage tooling (the tools application authors use to produce AppImages of their software) will have to be updated by the AppImage project, but even once it is, it will take considerable time until all application authors release updated AppImages of their software.

Hence, asking for a defined grace period until fuse2 gets removed from the Ubuntu Live ISO.

<текстареа style="width: 100%" rows="10">Apparently this affects most if not all flavors of Ubuntu. Especially the default flavor.

The AppImage format for distributing applications is centered around the idea that a user can boot the Ubuntu Live ISO, download an application in AppImage format, make it executable, and run it without having to install anything.

Not having libfuse2 and fusermount on the Live ISO breaks this for all existing AppImages out there.

AppImage tooling (the tools application authors use to produce AppImages of their software) will have to be updated by the AppImage project, but even once it is, it will take considerable time until all application authors release updated AppImages of their software.

Hence, asking for a defined grace period until fuse2 gets removed from the Ubuntu Live ISO.Revision history for this message

Launchpad Janitor (janitor)
wrote
on 2022-03-27:
#4

Status changed to ‘Confirmed’ because the bug affects multiple users.

<текстареа style="width: 100%" rows="10">Status changed to ‘Confirmed’ because the bug affects multiple users.

Changed in lubuntu-meta (Ubuntu):
status: New → Confirmed
Changed in ubuntu-budgie-meta (Ubuntu):
status: New → Confirmed
Changed in ubuntu-meta (Ubuntu):
status: New → Confirmed
Changed in ubuntukylin-meta (Ubuntu):
status: New → Confirmed

fossfreedom (fossfreedom)

on 2022-03-27

Changed in ubuntu-budgie-meta (Ubuntu):
status: Confirmed → Fix Released

Norbert (nrbrtx)

on 2022-04-07

tags: added: jammy

Revision history for this message

Steve Langasek (vorlon)
wrote
on 2022-05-05:
#8

fuse has been demoted from Ubuntu main in favor of fuse3; it would not be appropriate to re-promote it to main and expand the security surface of a default Ubuntu install (fuse is a very security-relevant facility), and Ubuntu images build only from main. So this is a wontfix for the Ubuntu desktop, libfuse2 is not going to be brought back into the default install and users who want to use libfuse2-dependent AppImages will need to install this library themselves beforehand.

Our community flavors are free to make their own decisions about whether to bundle libfuse2 by default, as several of them did before the release.

<текстареа style="width: 100%" rows="10">fuse has been demoted from Ubuntu main in favor of fuse3; it would not be appropriate to re-promote it to main and expand the security surface of a default Ubuntu install (fuse is a very security-relevant facility), and Ubuntu images build only from main. So this is a wontfix for the Ubuntu desktop, libfuse2 is not going to be brought back into the default install and users who want to use libfuse2-dependent AppImages will need to install this library themselves beforehand.

Our community flavors are free to make their own decisions about whether to bundle libfuse2 by default, as several of them did before the release.

Changed in ubuntu-meta (Ubuntu):
status: Confirmed → Won’t Fix
Changed in ubuntu-meta (Ubuntu Jammy):
status: Confirmed → Won’t Fix

See full activity log

To post a comment you must log in.

  • Report a bug

This report contains
Public
information
 

Everyone can see this information.

      You are

      not directly subscribed to this bug’s notifications.

      Subscribing…

      • Edit bug mail

      Как исправить ошибку?

      1. Библиотека не установлена

      Первый вариант, тут все понятно, библиотеки просто нет в системе, поэтому мы и получаем такую ошибку. Верный способ ее решения – просто найти пакет библиотеки с помощью пакетного менеджера и установить ее. Обычно, пакеты с библиотеками называются так же, как и сами библиотеки с префиксом lib.

      Например, если нам не хватает библиотеки libfuse2.so, то мы можем найти ее в Ubuntu такой командой:

      sudo apt search libfuse2

      Затем осталось только установить ее:

      sudo apt install libfuse2

      Если перед вами стоит задача собрать программу из исходников, то вам понадобится не только установить саму библиотеку, но и заголовочные файлы для нее:

      sudo apt install libfuse-dev

      И так для любой библиотеки. Но это не всегда помогает.

      2. Библиотека находится не в том каталоге

      Бывает что библиотека установлена, мы установили ее или она поставлялась вместе с программой, но ошибка как была, так и есть. Причиной этому может быть то, что загрузчик Linux не может найти библиотеку.

      Поиск библиотек выполняется по всех папках, которые указаны в конфигурационных файлах /etc/ld.conf.d/. По умолчанию, это такие каталоги, как /usr/lib, /lib, /usr/lib64, /lib64. Если библиотека установлена в другой каталог, то, возможно, это и есть причина проблемы.

      Вы можете посмотреть какие библиотеки сейчас доступны загрузчику с помощью команды:

      ldconfig -p

      Найти, где находится ваша библиотека можно с помощью команды locate. Например, нас интересует библиотека librtfreader.so:

       locate librtfreader

      Теперь мы знаем, что она находится по адресу /opt/kingsoft/wps-office/office6/. А значит, для работы программы необходимо сделать чтобы загрузчик библиотек ее видел. Для этого можно добавить путь в один из файлов /etc/ld.so.conf.d/ или же в переменную LD_LIBRARY_PATH:

      export LD_LIBRARY_PATH=/opt/kingsoft/wps-office/office6/

      Опять же, так вы можете поставить с любой библиотекой, которая взывает ошибку. Еще один более простой метод – это просто создать символическую ссылку на нужную библиотеку в правильной папке:

      ln -s /opt/kingsoft/wps-office/office6/librtfreader.so /usr/lib/librtfreader.so

      Источники

      • https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965636
      • https://losst.pro/oshibka-error-while-loading-shared-libraries
      [свернуть]
      Решите Вашу проблему!


      ×
      Adblock
      detector