Connected Google account, but Drive is not shown

[Zalán Hári]

After the recent updates of Ubuntu 24.04 Noble Numbat, Nautilus is unable to access Google Drive: it is not shown. I cannot find any error message in the logs.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-online-accounts 3.50.0-4ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 18 06:56:05 2024
InstallationDate: Installed on 2023-07-05 (288 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

[Jeremy Bícha (jbicha)]

I believe there is an upgrade issue where you need to reauthenticate in Settings > Online Accounts after upgrading to gnome-online-accounts 3.49/3.50 (which will happen when upgrading to Ubuntu 24.04 LTS).

Could you check if this fixes your issue? If it does, we can use this bug to track that upgrade issue.

[Zalán Hári (zalanhari)]

Thank you, I checked it by removing the accounts and adding them again, but it does not work.

[Jeremy Bícha (jbicha)]

The extra info in your original bug report says that your install was originally with Ubuntu 20.04 LTS but there is no upgrade log for upgrading to Ubuntu 24.04 LTS which I think means that you did not use update-manager or do-release-upgrade to do the upgrade.

I don't know if that affects how gnome-online-accounts is working for you. I was able to add my Google account to GNOME Online Accounts successfully and it shows up in my Nautilus file browser in the left sidebar in the second section from the top (listed after Trash).

[Zalán Hári (zalanhari)]

It is a bug, in my former reports, it was correct. I upgraded both times with update-manager (I usually prefer terminal, but for that, graphics is necessary for me), and in my first bug reports, it was correct. I will need to debug apport-bug :–).

Probably one of my agressive dist-upgrades for held packages has broken it.