Bug#1101025: gvfs-fuse: gvfsd-fuse daemon refuses to start
Simon McVittie
smcv at debian.org
Sat Mar 22 15:27:44 GMT 2025
On Sat, 22 Mar 2025 at 13:34:36 +0100, László Böszörményi (GCS) wrote:
> Quick check done. It seems in the past FUSE capabilities were a 32
>bit bitfield. It was moved to a 64 bit struct, causing an ABI break.
>It was handled by the SONAME bump and more importantly the FUSE helper
>functions started to use the new bitfield. See the mentioned bitfield
>comments [1][2] in the FUSE header. Both say use the FUSE helper
>functions fuse_set_feature_flag() and fuse_unset_feature_flag()
>instead of accessing internal parts directly.
>But then gvfs (even the one in Trixie / Sid) manipulates the old 32
>bit bitfield directly [3] (and at other places). Meaning it is a gvfs
>bug, a proposed fix is already provided [4].
>In very short, gvfs needs to be fixed. I can't do anything on the FUSE side
I think your footnotes have got lost?
Is [4] perhaps meant to point to commit "fuse: use
fuse_(un)set_feature_flag instead of setting manually" from
<https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/248>?
smcv
More information about the pkg-gnome-maintainers
mailing list