paru -S gnome-online-accounts-googledrive gvfs-googledrive
# It will say that it conflicts with existing packages, that's okay. Let it remove the old ones.
Hello @fluhus ! Awesome work! Thanks for reviving support for this much needed feature. In your copr repo, could you please also provide builds for Fedora 44 aarch64 packages? This would be very useful for Asahi Fedora systems.
@zheltikov I’ve built the packages for f44-aarch64, but I haven’t tested them yet because I’m not sure how without an aarch64 machine. You should be able to install it now, just please be careful, and please let me know how it works for you!
Ubuntu people, you are not forgotten! I’m still figuring out how to create PPAs for these packages. It’s more complicated than I expected. Will update here when it’s ready.
The Fedora 44 aarch64 packages work great! The Google Drive mount seems to disconnect quite often, probably because of my less-than-ideal cellular connection… But I remember the previous/original gvfs version working more stable.
Thank you @fluhus ! Looking forward to future updates!
sudo add-apt-repository ppa:fluhus/gnome-googledrive
sudo apt update
sudo apt install gnome-online-accounts gvfs
# You might need to log out and in again after installing.
Thank you for the feedback! Sorry you’re experiencing these hiccups.
Network issues might be the reason, but let’s make sure it’s not a software issue:
You can run journalctl --user -b | grep -iE 'gvfs|goa|google' and check if you’re spotting any crashes or errors.
If you are comfortable with running virtual machines, you can run f43 on a VM (with the old builtin Google Drive integration) and see if these hiccups repeat.
The updated Fedora 44 aarch64 packages work great: no evident issues or crashes during my usual workflow (downloading, uploading, moving, renaming, deleting files, etc.). Looking forward to this getting merged. Thanks, @fluhus !
Hi @fluhus. This is absolutely fantastic. Installing on my F44 system now. I noticed that, when downloading Google Docs, Slides, and Sheets, you appear to prefer Microsoft formats for download. Is it possible to configure your implementation to pull down ODT/ODS/ODP? If not, could this be considered because of the ubiquity of LibreOffice? and because it is an open standard rather than Microsoft’s? Or, does Google export better representations of their files in Microsoft formats, even with whatever conversion that LibreOffice or similar will do? Or, is this for another reason which I’m not thinking of? Thanks in advance, and really appreciate your work.
Really miss this feature and it’s awesome that we have the progress with implementing this feature! Tested it out and the auth and mounting process went well, but in the mounted FUSE directory I see the file ids instead of file names, so the content looks like this:
Hi @ntcarver, thanks for the feedback! Yes, the current implementation defaults to MS Office formats. This is meant to replicate the web UI’s behavior - when you click ‘Download’ on a native file it downloads it as an MS Office file. The idea is to maintain as much consistency with the web UI as possible and create fewer surprises to people coming from it.
However, I can see why exporting open formats would make sense in a Linux setting, where LibreOffice is prevalent. Perhaps this behavior could be configurable. Off the top of my head I’m thinking maybe a gsettings option for the export format can be a good solution - keeps the default behavior and is easy to change. If anyone has any other ideas for this please let me know.
Hi @Murz, thanks for the input! Yes, what you are seeing does look weird. This is how it worked in the previous implementation too. I think the reason for this is that Google Drive allows files with the same name in the same folder, so GIO uses their unique file IDs as display names. At the moment I’m not sure how to solve this.
You can, however, use their “regular” names in your input, for example:
Awesome. Yes, a setting would be great. Also, managed to get a rate limit exceeded copying a bunch of junk into an archive folder… whoops LOL. On a more serious note, when creating directories in Files, I get two duplicate directories. Refreshing clears it. Anything I can do to help track down this issue?
Maybe we can just add (N) suffixes to the file names, which are the duplicates? So, when we are building the list of files, display the first unique file name as is, and if there is a duplicate of the already displayed name, add (1) suffix to the file name, and so on. This is how many Google Drive sync tools work like InSync, RClone, ExpanDrive, etc.