GNOME 50 removes Google Drive support from Nautilus after libgdata went unmaintained for four years, with no volunteers stepping up to maintain the integration.
GNOME 50 will ship without Google Drive integration in its file manager, Nautilus, after the underlying library that powered the feature went unmaintained for nearly four years.
As reported by OMG Ubuntu, a user on the GNOME Discourse forum noticed the missing functionality in a Fedora 44 beta build. While mail, contacts, and calendar integrations through GNOME Online Accounts (GOA) still work, the Google Drive option no longer functions.
Emmanuele Bassi of the GNOME Team confirmed this was intentional, not a bug: "It is no longer supported, unfortunately. Libgdata, which was used to handle integration with some Google online services, has been unmaintained for nearly 4 years. GVFS has disabled the dependency by default 10 months ago, and GNOME Online Accounts checks for that."
The removal highlights a common challenge in open-source development: maintaining third-party integrations requires ongoing effort. When libgdata stopped receiving updates, GVFS (the virtual filesystem that powers GNOME's cloud storage features) disabled it by default. Despite this being known for months, no volunteers stepped forward to maintain the Google Drive integration.
This decision affects users who relied on browsing and managing Google Drive files directly through Nautilus. Those users will need to either use Google's web interface, install third-party tools, or switch to desktop environments that maintain different cloud storage integrations.
GNOME 50 continues GNOME's push toward Wayland-only operation and modern Linux desktop standards, but this change serves as a reminder that even popular features can disappear when maintenance resources aren't available. The team appears to have given ample warning through the GVFS deprecation before making the final cut in the stable release.
The removal doesn't affect other Google services integrated through GOA, suggesting those components have more active maintenance or simpler requirements that make them easier to keep current with Google's API changes.
Comments
Please log in or register to join the discussion