Date: Sun, 23 Oct 2022 16:12:31 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 267270] devel/gvfs: Make gvfsd-trash optional Message-ID: <bug-267270-6497-LUm1gC4YF9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267270-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-267270-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267270 --- Comment #2 from Sean Champ <lab+bsd@thinkum.space> --- Just adding an observation: With gvfsd-trash unavailable, some file managers might assume gvfsd is not available - seen with x11-fm/nemo at version 5.4.3 with patch https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267244 At least, nemo presents the message: "It looks like gvfs is not available," under the Advanced tab in the nemo preferences dialog. Ideally, the gvfs plugins that are installed would still be available and usable by nemo, regardless of what's activated the message in the prefs dialog. Checking the process list, a number of gvfs volume monitor plugins are runn= ing, even with gvfsd-trash not installed. In my own opinion, this would not negatively affect the operations of a nor= mal FreeBSD desktop. Perhaps it may affect the availability of filesystems via = gvfs plugins, in some file managers. From the perspective of FreeBSD official po= rts, then after my initial patch and with this known side-effect, I'd understand= if gvfsd-trash would be installed by default. afaict gvfs is still functional, even without that particular component installed --=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-267270-6497-LUm1gC4YF9>