Description of problem:

The gvfs-daemon process is starting by default for the root user, even if the root user is not logged into the system console. 

$ runlevel 
5 3

$ ps aux | grep gvfs
root        2895  0.0  0.6 312916  9408 ?        Ssl  18:26   0:00 /usr/libexec/gvfsd
root        3510  0.0  0.0  12136  1152 pts/0    R+   18:27   0:00 grep --color=auto gvfs

As per the journal logs, the gvfs-daemon process for root was started by "flatpak --installations". 

$ less var/log/messages |grep gvfs-daemon
Mar 24 05:42:14 hostname dbus-daemon[62961]: [session uid=0 pid=62961] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.1' (uid=0 pid=62949 comm="gdk-pixbuf-query-loaders-64 --update-cache " label="unconfined_u:unconfined_r:rpm_script_t:s0-s0:c0.c1023")
May 28 11:44:23 hostname dbus-daemon[43240]: [session uid=0 pid=43240] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.1' (uid=0 pid=43238 comm="flatpak --installations ")

The issue is reproducible on RHEL8.2 and above systems.

Version-Release number of selected component (if applicable):
gvfs-1.36.2-8.el8.x86_64
flatpak-1.6.2-2.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Reboot the system in multi-user.target
2. Login into the system via ssh and check the status.

    # ps aux | grep gvfs

Actual results:
gvfsd process starts for root user

Expected results:
gvfsd process should not start 

Additional info:

As per the following link the problem was caused by the flatpak installations and the fix is available in the upstream:

    https://github.com/flatpak/flatpak/commit/f69a35ceec7322e02007b45d676e0b6f1e9376b0