For a few days now, I’m encountering issues with Google Drive on my Fedora 41 Workstation with Gnome:
from time to time, one of my Google Drives disconnect itself
probably related to the above issue, I can see an error called “gvfsd-google killed by SIGSEGV”
when connected, the drive is responsive normally, but the simlinks related to files in that drive are very slow to show up and to show updates in the gnome files GUI
probably related to issue 3., KeePassXC is very slow at opening simlinks of databases saved on this Google Drive and can’t save updates (software uses a full CPU and does not stop, the database recorded on GDrive is empty)
I’m connected to this Google Drive via the Gnome preferences.
While you’re waiting for an answer to the issue itself, let my share you my experience.
In the past I have tested the integration of several cloud drive platforms (Google Drive, Nextcloud, standard WebDav etc) into the GNOME desktop, and my conclusion was that symlinks are not reliable, and that accessing the cloud files directly (via mounted drives) doesn’t provide an experience (from a performance perspective) worth using other than occasionally.
What I have ended up doing is configuring an rclone remote[1] and using its bisync (so 2-way sync) functionality, which even though in an almost-forever-beta state, is reliable enough for my needs. And of course, the files being local, performance is as good as it gets. In order to be in control, I didn’t create a systemd timer, but rather running the command from time to time[2] via a bash alias, so that I can see potential issues/conflicts as they happen.
My WebDav remote doesn’t even suppport Modtime compare, but Google Drive does, IIRC. ↩︎
At least when sitting down to the computer and then again when leaving it. ↩︎