Your message dated Mon, 26 May 2025 15:19:20 +0000 with message-id <e1ujzbk-009waz...@fasolo.debian.org> and subject line Bug#1101305: fixed in fuse3 3.17.2-2 has caused the Debian Bug report #1101305, regarding libfuse3-4: regression in 3.17.1-1 for gvfsd-fuse: "both 'want' and 'want_ext' are set" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1101305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libfuse3-4 Version: 3.17.1-1 Severity: serious Justification: regression in code that is (AFAICS) following upstream recommendations X-Debbugs-Cc: Michael Anderson <doctorkills...@yahoo.com>, Vladimir K <pzs...@yandex.ru> Control: affects -1 + src:gvfs gvfs-fuse On Tue, 25 Mar 2025 at 09:34:40 +0000, Michael Anderson wrote: >Thanks for the previous fix which did work. > >However it has broken again with libfuse3-4 updating from 3.17.1~rc1-3 >to 3.17.1-1. On Tue, 25 Mar 2025 at 14:17:32 +0300, Vladimir K wrote: >It worked, but broke again. > > $ eng apt list --installed fuse3 gvfs-fuse libfuse* > fuse3/unstable,now 3.17.1-1 amd64 [installed,automatic] > gvfs-fuse/unstable,now 1.57.2-2 amd64 [installed] > libfuse2t64/unstable,now 2.9.9-9 amd64 [installed,automatic] > libfuse3-4/unstable,now 3.17.1-1 amd64 [installed,automatic] > > $ /usr/libexec/gvfsd-fuse -f /run/user/1000/gvfs > fuse: both 'want' and 'want_ext' are set Laszlo, I assume this is not the result you expected after updating fuse3? In gvfs-fuse_1.57.2-2, the only references to FUSE_CAP are: client/gvfsfusedaemon.c: fuse_set_feature_flag(conn, FUSE_CAP_ATOMIC_O_TRUNC); client/gvfsfusedaemon.c: fuse_unset_feature_flag(conn, FUSE_CAP_ASYNC_READ); which if I understand correctly is the style that is recommended by the upstream developers of FUSE. I verified that this worked as intended with libfuse3-4_3.17.1~rc1-3, but I can confirm the regression with 3.17.1-1. If necessary we can revert to the old code in gvfs as a workaround: conn->want |= FUSE_CAP_ATOMIC_O_TRUNC; conn->want &= ~FUSE_CAP_ASYNC_READ; but I'm aware that that's unlikely to be very future-proof, and I'd like to avoid getting into a cycle of fuse3 and gvfs working around each other! Thanks, smcv
--- End Message ---
--- Begin Message ---Source: fuse3 Source-Version: 3.17.2-2 Done: Laszlo Boszormenyi (GCS) <g...@debian.org> We believe that the bug you reported is fixed in the latest version of fuse3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1101...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) <g...@debian.org> (supplier of updated fuse3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Mon, 19 May 2025 20:39:08 +0200 Source: fuse3 Architecture: source Version: 3.17.2-2 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) <g...@debian.org> Changed-By: Laszlo Boszormenyi (GCS) <g...@debian.org> Closes: 1101305 1105099 1105150 Changes: fuse3 (3.17.2-2) unstable; urgency=medium . [ Laszlo Boszormenyi (GCS) ] * Backport upstream fixes (closes: #1101305): - make conn->want/want_ext conversion non fatal, - add container_of and ROUND_UP macros, - conn->want conversion: fix fuse_apply_conn_info_opts() . * Update symbols file (closes: #1105099). . [ Helmut Grohne <hel...@subdivi.de> ] * Update -latomic architecture list (closes: #1105150). Checksums-Sha1: 02f8485db00b7809c379d3a60ee367468e5a9c0a 2428 fuse3_3.17.2-2.dsc 6b723e14a90380858c717f5b10b3827eea65f0fa 18644 fuse3_3.17.2-2.debian.tar.xz Checksums-Sha256: c3eeb57b5eca0e2e1c0fe1f47d461dd7132456a3af5cbb87026bb7b419af1787 2428 fuse3_3.17.2-2.dsc 6a6d0a6b7f3b469c0b5c23be25c2198bf1e184a838d10185e1afc82c43047083 18644 fuse3_3.17.2-2.debian.tar.xz Files: c01902c01e54bb93d8c52e0c63e15101 2428 utils optional fuse3_3.17.2-2.dsc cfd3a3572ca944e584949d63dffd9583 18644 utils optional fuse3_3.17.2-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmg0f+gACgkQ3OMQ54ZM yL8AGQ/8DOzG0Ebt92P92hs8KtRDjbfz2eqSq+LLj/glmJ1A7CH1Q5oOHjiq9oY9 0FlOS0FC0/V+pHhXJk5efqahE7XPiSDVPNz2TKMB+yy8VhV41UW8RRGrMxJ7T35+ 8FbMKavx3nEtvv1XwdL99D7h1QHwwS43Ts/vTlSeFyLV/FUh4f62iRug7I5krfdZ eALtamw+Hn+MD4wzr7XjDULafTyxpy0phyqjoCMAZCpBaRiCvu8W8wGDymtPRnYG DoQ8TbqxoS13H+t/YmEepLZlFNb2JyuyXnPhp1nDh7LxI+tjwQpSbdFwdicvvfFu IWMBZ4aFRP5n5IdQN4cZRR/AMAE8NMPavRLmlMnr65/YWfmC8uxX+RjYP431Kt4p nXrzMN+4KyTEbUh1z5DydfjVfj2Id5SAm0CP5nzA3E/CtA7oZuPGgnb0khfNpd5l nCUyPXd0BB423ZNXd1o5HSMDVLhDDNkqLP57xnmztX6AhLPtREo5Xp2Z2rvb4ocY XUescBFGKmhMjucJV0xBY7miFYV6OxE9Bemetk61qhy3Hdd6LfddOr7T3iKzpT3D NGylnuAOK8quBpAJX9MDjawOQQQwInOls5AOCPOoaTI9sZYt2CnwfGhOz5tEGCXB UarKDsDk7DJ0Tmowa1LKmUAmg2NcFdywyFPi+A6UVf5jGI0BWTA= =fpwf -----END PGP SIGNATURE-----
pgphFtFlvMBZP.pgp
Description: PGP signature
--- End Message ---
