Devuan bug report logs - #738
Missing symbol fuse_new_31

Package: libfuse3-3; Reported by: [email protected]; Owned by: Andreas Messer <[email protected]>; Keywords: debian upstream; Done: Mark Hindley <[email protected]>; Maintainer for libfuse3-3 is (unknown).

Message received at [email protected]:

Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Date: Sun, 29 Jan 2023 13:37:18 +0000
From: Mark Hindley <[email protected]>
To: Ferenc =?iso-8859-1?B?R+Fs?= <[email protected]>
Cc: [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <CAFUqQPDzh9ri=Xv8-8t6VE4mHxYmGudd0JwA_Lafne3W=iVVUg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAFUqQPDzh9ri=Xv8-8t6VE4mHxYmGudd0JwA_Lafne3W=iVVUg@mail.gmail.com>

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

Notification sent to [email protected]:
bug acknowledged by developer. Full text available.

Reply sent to Mark Hindley <[email protected]>:
You have taken responsibility. Full text available.

Message received at [email protected]:

Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::1132; helo=mail-yw1-x1132.google.com; [email protected]; receiver=<UNKNOWN> 
MIME-Version: 1.0
References: <[email protected]>
 <[email protected]> <[email protected]> <[email protected]>
In-Reply-To: <[email protected]>
From: =?UTF-8?Q?Ferenc_G=C3=A1l?= <[email protected]>
Date: Sun, 29 Jan 2023 14:17:33 +0100
Message-ID: <CAFUqQPDzh9ri=Xv8-8t6VE4mHxYmGudd0JwA_Lafne3W=iVVUg@mail.gmail.com>
Subject: Re: bug#738: actually libfuse3-3
To: Mark Hindley <[email protected]>
Cc: [email protected]
Content-Type: multipart/alternative; boundary="000000000000fa698f05f366ee76"

--000000000000fa698f05f366ee76
Content-Type: text/plain; charset="UTF-8"

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 <[email protected]> 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/
>
>

--000000000000fa698f05f366ee76
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Mark,<div><br></div><div>yes the issue is solved and th=
e exception message is gone after the upgrade.</div><div><br></div><div>Tha=
nks.</div><div><br></div><div>Regards,</div><div>Ferenc</div></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 27=
, 2023 at 3:15 PM Mark Hindley &lt;<a href=3D"mailto:[email protected]">m=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">Ferenc,<br>
<br>
On Wed, Jan 25, 2023 at 07:31:17PM +0000, Mark Hindley wrote:<br>
&gt; Alternatively, fuse3 3.13 should migrate to testing in 2 days[2], whic=
h<br>
&gt; should fix it.<br>
<br>
Debian migrated fuse3 3.13.0-2 to testing[1] this morning. Does upgrading t=
o<br>
that version of libfuse3-3 resolve this bug for you?<br>
<br>
Thanks<br>
<br>
Mark<br>
<br>
[1]=C2=A0 <a href=3D"https://tracker.debian.org/news/1413829/fuse3-3130-2-m=
igrated-to-testing/" rel=3D"noreferrer" target=3D"_blank">https://tracker.d=
ebian.org/news/1413829/fuse3-3130-2-migrated-to-testing/</a><br>
<br>
</blockquote></div>

--000000000000fa698f05f366ee76--

Acknowledgement sent to Ferenc Gál <[email protected]>:
Extra info received and forwarded to list. Copy sent to [email protected], Andreas Messer <[email protected]>. Full text available.

Information forwarded to [email protected], [email protected], Andreas Messer <[email protected]>:
bug#738; Package libfuse3-3. Full text available.

Message received at [email protected]:

Received: (at 738) by bugs.devuan.org; 27 Jan 2023 14:16:33 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 27 Jan 2023 14:16:33 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id dY4LB4Hc02PrRwAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Fri, 27 Jan 2023 14:15:29 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 121B3597; Fri, 27 Jan 2023 14:15:28 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 0C3F592
	for <[email protected]>; Fri, 27 Jan 2023 14:15:23 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pLPVh-0004vC-GI; Fri, 27 Jan 2023 14:15:21 +0000
Received: (nullmailer pid 5591 invoked by uid 1000);
	Fri, 27 Jan 2023 14:15:21 -0000
Date: Fri, 27 Jan 2023 14:15:21 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
X-Debbugs-No-Ack: No Thanks

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/

Information forwarded to [email protected], [email protected], Andreas Messer <[email protected]>:
bug#738; Package libfuse3-3. Full text available.

Changed bug title to 'Missing symbol fuse_new_31' from 'Fwd: libvirtd'. Request was from Mark Hindley <[email protected]> to [email protected]. Full text available.

Added tag(s) upstream and debian. Request was from Mark Hindley <[email protected]> to [email protected]. Full text available.

Added indication that 738 affects libvirt-daemon-driver-lxc Request was from Mark Hindley <[email protected]> to [email protected]. Full text available.

Marked as fixed in versions 3.13.0-1. Request was from Mark Hindley <[email protected]> to [email protected]. Full text available.

Marked as found in versions 3.12.0-1. Request was from Mark Hindley <[email protected]> to [email protected]. Full text available.

No longer marked as found in versions 8.10.0-3devuan1. Request was from Mark Hindley <[email protected]> to [email protected]. Full text available.

bug reassigned from package 'libvirt-daemon-driver-lxc' to 'libfuse3-3'. Request was from Mark Hindley <[email protected]> to [email protected]. Full text available.

Message received at [email protected]:

Received: (at 738) by bugs.devuan.org; 25 Jan 2023 19:31:34 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 19:31:34 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id Qu9rLIyD0WNMYQAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 19:31:24 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AAE4C597; Wed, 25 Jan 2023 19:31:24 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id AC5F7396
	for <[email protected]>; Wed, 25 Jan 2023 19:31:19 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pKlUL-0005ln-Ub; Wed, 25 Jan 2023 19:31:18 +0000
Received: (nullmailer pid 16599 invoked by uid 1000);
	Wed, 25 Jan 2023 19:31:17 -0000
Date: Wed, 25 Jan 2023 19:31:17 +0000
From: Mark Hindley <[email protected]>
To: [email protected], [email protected]
Subject: Re: bug#738: actually libfuse3-3
Message-ID: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

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) <[email protected]>  Sun, 22 Jan 2023 08:17:08 +0100

fuse3 (3.13.0-1) unstable; urgency=medium

  * New upstream release.

 -- Laszlo Boszormenyi (GCS) <[email protected]>  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) <[email protected]>  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

Acknowledgement sent to Mark Hindley <[email protected]>:
Extra info received and forwarded to list. Copy sent to Andreas Messer <[email protected]>. Full text available.

Information forwarded to [email protected], Andreas Messer <[email protected]>:
bug#738; Package libvirt-daemon-driver-lxc. Full text available.

Owner recorded as Andreas Messer <[email protected]>. Request was from Andreas Messer <[email protected]> to [email protected]. Full text available.

Changed bug submitter to '[email protected]' from 'Andreas Messer <[email protected]>'. Request was from Andreas Messer <[email protected]> to [email protected]. Full text available.

Message received at [email protected]:

Received: (at submit) by bugs.devuan.org; 25 Jan 2023 18:45:23 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 25 Jan 2023 18:45:23 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id xyDEIXd40WM3YAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Wed, 25 Jan 2023 18:44:07 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 77BD1597; Wed, 25 Jan 2023 18:44:07 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=ham
	autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a03:4000:24:9b0::1; helo=nyx.bastelmap.de; [email protected]; receiver=<UNKNOWN> 
Received: from nyx.bastelmap.de (nyx.bastelmap.de [IPv6:2a03:4000:24:9b0::1])
	by email.devuan.org (Postfix) with ESMTPS id 0B417396
	for <[email protected]>; Wed, 25 Jan 2023 18:44:01 +0000 (UTC)
Received: from zeus (p200300fb97029c001dfcf8a5c3f6af25.dip0.t-ipconnect.de [IPv6:2003:fb:9702:9c00:1dfc:f8a5:c3f6:af25])
	by nyx.bastelmap.de (Postfix) with ESMTPSA id 297671EAD2A
	for <[email protected]>; Wed, 25 Jan 2023 19:44:01 +0100 (CET)
Date: Wed, 25 Jan 2023 19:43:55 +0100
From: Andreas Messer <[email protected]>
Subject: Fwd: libvirtd
To: [email protected]
Message-Id: <[email protected]>
References:
	<CAFUqQPDvY=wN5Q044chkhEBPBgJn6g7jNvMkgXyGd8edQW0m=A@mail.gmail.com>
X-Mailer: geary/3.38.1
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

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


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

---------- Weitergeleitete Nachricht ----------
Von: Ferenc G=E1l <[email protected]>
Betreff: libvirtd
Datum: 2023-01-24T21:31:49+0100
An: [email protected]

Hi,

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

root@HomePC:~# libvirtd
2023-01-24 20:12:17.468+0000: 12717: info : libvirt version: 8.10.0,=20
package: 3devuan1 (Andreas Messer <[email protected]> Wed, 18 Jan 2023=20
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 :=20
internal error: Failed to load module=20
'/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so'=
:=20
/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_lxc.so:=20
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=20
(2023-01-07) x86_64 GNU/Linux

Thanks,
Ferenc

Acknowledgement sent to Andreas Messer <[email protected]>:
New bug report received and forwarded. Full text available.

Report forwarded to [email protected]:
bug#738; Package libvirt-daemon-driver-lxc. Full text available.

Devuan bug report logs - #738 Missing symbol fuse_new_31

Message received at [email protected]:

Message received at [email protected]:

Message received at [email protected]:

Message received at [email protected]:

Message received at [email protected]:

Devuan bug report logs - #738
Missing symbol fuse_new_31