Devuan bug report logs - #738
Missing symbol fuse_new_31

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

Package: libvirt-daemon-driver-lxc
Version: 8.10.0-3devuan1


Here is a report from a user with symbol resolve issue. According our 
build log
8.10.0-3devuan1 was build with libfuse3-dev 3.13.0-2. However, in 
daedalus repos
we have libfuse3 3.12.0-1. Here is the original report:

---------- Weitergeleitete Nachricht ----------
Von: Ferenc Gál <gferenc88@gmail.com>
Betreff: libvirtd
Datum: 2023-01-24T21:31:49+0100
An: andi@bastelmap.de

Hi,

i have noticed an issue with the libvirt daemon or lxc package on 
Devuan testing:

root@HomePC:~# libvirtd
2023-01-24 20:12:17.468+0000: 12717: info : libvirt version: 8.10.0, 
package: 3devuan1 (Andreas Messer <andi@bastelmap.de> Wed, 18 Jan 2023 
19:20:27 +0100)
2023-01-24 20:12:17.468+0000: 12717: info : hostname: HomePC
2023-01-24 20:12:17.468+0000: 12717: error : virModuleLoadFile:53 : 
internal error: Failed to load module 
'/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so': 
/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so: 
undefined symbol: fuse_new_31, version FUSE_3.1

Installed FUSE:
root@HomePC:~# apt search fuse3
Sorting... Done
Full Text Search... Done
fuse3/testing,now 3.12.0-1 amd64 [installed,automatic]
 Filesystem in Userspace (3.x version)

libfuse3-3/testing,now 3.12.0-1 amd64 [installed,automatic]
 Filesystem in Userspace (library) (3.x version)

libfuse3-dev/testing 3.12.0-1 amd64
 Filesystem in Userspace (development) (3.x version)

python3-pyfuse3/testing 3.2.1-2+b1 amd64
 Python 3 bindings for libfuse 3 with asynchronous API

uname -a
Linux HomePC 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 
(2023-01-07) x86_64 GNU/Linux

Thanks,
Ferenc

Message #14 received at 738@bugs.devuan.org (full text, mbox, reply):

Control: reassign -1 libfuse3-3
Control: found -1 3.12.0-1
Control: fixed -1 3.13.0-1
Control: affects -1 libvirt-daemon-driver-lxc
Control: tags -1 debian upstream

Ferenc and Andreas,

At first sight this is odd and looks as if a library transition might have been
missed in Debian. However, Debian's fuse3 changelog shows no symbol changes
between 3.12 and 3.13:

fuse3 (3.13.0-2) unstable; urgency=medium

  * Can't run self-testing on big-endian machines.

 -- Laszlo Boszormenyi (GCS) <gcs@debian.org>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <gcs@debian.org>  Tue, 17 Jan 2023 19:11:25 +0100

fuse3 (3.12.0-1) unstable; urgency=medium

  * New upstream release.
  * Update library symbols for this release.
  * Update watch file.
  * Update Lintian overrides.
  * Update Standards-Version to 4.6.1 .

 -- Laszlo Boszormenyi (GCS) <gcs@debian.org>  Sat, 22 Oct 2022 21:28:52 +0200

So, looking at fuse3 upstream, it appears that fuse_new_31 was not defined when
HAVE_LIBC_VERSIONED_SYMBOLS was not set and recently fixed upstream[1].

That upstream fix is included in 3.13.

So I suspect this is a Debian bug in 3.12 where the symbol is not defined. I am
surprised that nobody else has bumped into it and reported it.

Alternatively, fuse3 3.13 should migrate to testing in 2 days[2], which
should fix it.

HTH

Mark

[1]  https://github.com/libfuse/libfuse/commit/d372d3f80b5437e652ea501d8a4a917f7001b9d7

[2]  https://qa.debian.org/excuses.php?package=fuse3

Message #31 received at 738@bugs.devuan.org (full text, mbox, reply):

Ferenc,

On Wed, Jan 25, 2023 at 07:31:17PM +0000, Mark Hindley wrote:
> Alternatively, fuse3 3.13 should migrate to testing in 2 days[2], which
> should fix it.

Debian migrated fuse3 3.13.0-2 to testing[1] this morning. Does upgrading to
that version of libfuse3-3 resolve this bug for you?

Thanks

Mark

[1]  https://tracker.debian.org/news/1413829/fuse3-3130-2-migrated-to-testing/

Message #36 received at 738@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi Mark,

yes the issue is solved and the exception message is gone after the upgrade.

Thanks.

Regards,
Ferenc

On Fri, Jan 27, 2023 at 3:15 PM Mark Hindley <mark@hindley.org.uk> wrote:

> Ferenc,
>
> On Wed, Jan 25, 2023 at 07:31:17PM +0000, Mark Hindley wrote:
> > Alternatively, fuse3 3.13 should migrate to testing in 2 days[2], which
> > should fix it.
>
> Debian migrated fuse3 3.13.0-2 to testing[1] this morning. Does upgrading
> to
> that version of libfuse3-3 resolve this bug for you?
>
> Thanks
>
> Mark
>
> [1]
> https://tracker.debian.org/news/1413829/fuse3-3130-2-migrated-to-testing/
>
>

[Message part 2 (text/html, inline)]

Message #41 received at 738-done@bugs.devuan.org (full text, mbox, reply):

Version: 3.13.0-1

On Sun, Jan 29, 2023 at 02:17:33PM +0100, Ferenc Gál wrote:
>    Hi Mark,
>    yes the issue is solved and the exception message is gone after the
>    upgrade.

Great. Thanks. Closing

Mark

Send a report that this bug log contains spam.