Comment # 4 on bug 980521 from Martin Szulecki

Ok, thanks. It kind of proves my point.

On systems with only a single "gvfsd" running after login everything works
normally as the DBUS session bus is the same.

On systems with two "gvfsd" running after login the issue comes up as
"gvfsd-fuse" doesn't get the mount messages most likely because it's using a
different DBUS session bus.

I can reproduce the issue on a clean openSUSE Tumbleweed Live CD system in a VM
(see screenshot). The other systems can not be considered absolutely clean
installs.

It isn't fixed after installing obs binary packages directly and I am
nevertheless using a branched GNOME:Factory "gvfs" with added debugging on
affected systems.

Also tested running the same system with nouveau instead of the NVIDIA blob and
got a single "gvfsd" with working mounts...

It smells like a nasty thing somewhere in the gdm/login/xsession process.