Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Mar 2021 06:29:10 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 254452] devel/gvfs: gvfsd-fuse needs FUSE_CAP_ATOMIC_O_TRUNC from fuse
Message-ID:  <bug-254452-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254452

            Bug ID: 254452
           Summary: devel/gvfs: gvfsd-fuse needs FUSE_CAP_ATOMIC_O_TRUNC
                    from fuse
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: gnome@FreeBSD.org
          Reporter: damjan.jov@gmail.com
             Flags: maintainer-feedback?(gnome@FreeBSD.org)
          Assignee: gnome@FreeBSD.org

59709: write(2,"fuse: error: filesystem requested capabilities 0x8 that are=
 not
supported by kernel, aborting.\n",95) =3D 95 (0x5f)

0x8 =3D FUSE_CAP_ATOMIC_O_TRUNC

gvfsd-fuse can be hacked into working, by remove this flag from its wanted
flags, through changing 1 line in
/usr/ports/devel/gvfs/files/patch-client_gvfsfusedaemon.c, from:

---snip---
+#ifdef FUSE_CAP_ATOMIC_O_TRUNC
---snip---

to:

---snip---
+#if 0
---snip---

But it would be better if fuse actually supported this.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254452-7788>