Description of problem:
gdm's gnome session starts gvfsd (and friends) and goa-daemon as user "gdm" - and I think they are not necessary for the login screen.


Version-Release number of selected component (if applicable):
gdm-3.16.1.1-1.fc22.x86_64
gnome-session-3.16.0-1.fc22.x86_64


How reproducible:
- Start f22 workstation
- login to GNOME (X or wayland session)
- look for gdm's processes
- find out that it has started it's own set of gvfs and goa processes


Additional info:
this may have to do with the fact that gdm-session-worker calls gnome-session with the --session gnome-wayland switch (which may pull in desktop services / daemons?)


output of "ps -u gdm":
  PID TTY          TIME CMD
  715 ?        00:00:00 systemd
  720 ?        00:00:00 (sd-pam)
  722 tty1     00:00:00 gdm-wayland-ses
  727 tty1     00:00:00 dbus-daemon
  733 tty1     00:00:00 gnome-session
  763 tty1     00:01:09 gnome-shell
  772 tty1     00:00:00 gvfsd
  776 tty1     00:00:00 gvfsd-fuse
  825 tty1     00:00:00 Xwayland
  844 tty1     00:00:00 at-spi-bus-laun
  847 tty1     00:00:00 dbus-daemon
  851 tty1     00:00:00 at-spi2-registr
  859 ?        00:00:00 pulseaudio
  897 tty1     00:00:00 gnome-settings-
  913 tty1     00:00:00 gvfs-udisks2-vo
  939 tty1     00:00:00 gvfs-afc-volume
  946 tty1     00:00:00 gvfs-gphoto2-vo
  950 tty1     00:00:00 gvfs-mtp-volume
  963 tty1     00:00:00 gvfs-goa-volume
  966 tty1     00:00:00 goa-daemon

gvfs and goa add up to about 10 MBs of additional RAM usage (which is not a lot, but still)