[Bug 267270] devel/gvfs: Make gvfsd-trash optional
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 267270] devel/gvfs: Make gvfsd-trash optional"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 23 Oct 2022 16:12:31 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267270 --- 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=267244 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 running, even with gvfsd-trash not installed. In my own opinion, this would not negatively affect the operations of a normal FreeBSD desktop. Perhaps it may affect the availability of filesystems via gvfs plugins, in some file managers. From the perspective of FreeBSD official ports, 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 -- You are receiving this mail because: You are the assignee for the bug.