GNOME Remote Storage Integration#

GNOME Online Accounts (GOA) and gvfs together form the two-layer stack that powers internet-based storage in GNOME Files (Nautilus) on Bluefin:

• GOA (goa-daemon) is the credential and account broker. It runs as a D-Bus session service (org.gnome.OnlineAccounts) and exposes each account as an object under /org/gnome/OnlineAccount/Accounts/. It handles OAuth2 token refresh, password retrieval from GNOME Keyring, and presents the account setup UI in GNOME Settings → Online Accounts. 1
• gvfs is the userspace virtual filesystem built on GIO/GLib. Its gvfs-goa-volume-monitor daemon watches the D-Bus for accounts that implement org.gnome.OnlineAccounts.Files and surfaces them as GVolume objects in the file chooser and GNOME Files sidebar. The actual file I/O is delegated to a backend-specific daemon (gvfsd-*). 2

GNOME Settings → GOA (goa-daemon) → D-Bus: org.gnome.OnlineAccounts.Files
                                           ↓
                        gvfs-goa-volume-monitor → GVolume in Nautilus
                                           ↓
                         gvfsd-google / gvfsd-dav / … ← actual I/O

Bluefin note: No custom configuration for GOA or gvfs was found in the Bluefin build layers. Both components ship as standard GNOME session services and work out of the box on the GNOME desktop.

Supported Providers (Files integration)#

Only providers that implement the org.gnome.OnlineAccounts.Files interface are mounted as virtual drives in GNOME Files. 3

4

WebDAV (manual mount): gvfs ships a dav backend (requires libsoup, libxml) that you can connect to directly in GNOME Files via Other Locations → Connect to Server using a dav:// or davs:// URL — no GOA account required. 5

Architecture: How a Mount Happens#

1. User adds an account in Settings → Online Accounts. goa-daemon stores credentials in GNOME Keyring. 6
2. gvfs-goa-volume-monitor detects the new account object on D-Bus and advertises a GVolume in GIO.
3. When the user opens GNOME Files or a file dialog, the volume appears in the sidebar. On first access gvfs auto-mounts it.
4. gvfs spawns the matching backend:
   • Google Drive → gvfsd-google (uses libgdata + libgoa) 7
   • Nextcloud / WebDAV → gvfsd-dav (uses libsoup + libxml) 8
5. The backend performs service-specific protocol I/O. Non-GIO apps can access mounts via the FUSE bridge at ~/.gvfs/ or /run/user/<uid>/gvfs/. 9

Key D-Bus Interfaces & Diagnostics#

10

Credential issues: Tokens and passwords live in GNOME Keyring. Use seahorse and search for goa to inspect stored credentials. Call EnsureCredentials on the D-Bus account object to validate token state. 6

gvfsd not running? Confirm gvfs-goa-volume-monitor is present and running with user privileges. Restart via systemctl --user restart gvfs-goa-volume-monitor. 11

Primary References#