start backend (mount and volume monitors) on demand
@genodeftest
Submitted by Christian Stadelmann Assigned to gvf..@..e.bugs
Link to original bug (#761878)
Description
Short description: GVFS starts a lot of processes. I don't need most of them.
Steps to reproduce: On a Fedora 23 installation in a gnome session I see these gvfs processes running by default:
gvfs-afc-volume-monitor gvfs-udisks2-volume-monitor gvfs-mtp-volume-monitor gvfs-gphoto2-volume-monitor gvfs-goa-volume-monitor gvfsd gvfsd-trash gvfsd-network gvfsd-metadata gvfsd-http gvfsd-fuse gvfsd-dnssd
Out of these, there are some core daemons: gvfsd gvfsd-metadata (probably important) gvfsd-trash and (probably) gvfs-udisks2-volume-monitor and (maybe) gvfsd-fuse for /run/user/1000 stuff
All the other processes will be used rarely or not at all. I don't do/have MTP, GPhoto2, GOA or AFC mounts. I don't share data via network (http). I don't need these processes running.
According to systemd, those processes are not running, but they are: $ systemctl --user status gvfs-mtp-volume-monitor.service ● gvfs-mtp-volume-monitor.service - Virtual filesystem service - Media Transfer Protocol monitor Loaded: loaded (/usr/lib/systemd/user/gvfs-mtp-volume-monitor.service; static; vendor preset: enabled) Active: inactive (dead)
syslog (journalctl) reveals they are started by gdm-{wayland,x}-session using dbus.
Affected version: gvfs-1.26.2-1.fc23.x86_64 glib2-2.46.2-1.fc23.x86_64 gdm-3.18.2-1.fc23.x86_64 gnome-shell-3.18.3-1.fc23.x86_64
PS: I might be wrong assigning this bug to gvfs, but I haven't found any configuration for this, so it looks like this is the default behaviour.
Version: 1.26.x