Skip to content

upgrading to 3.52.4-1 breaks Google sign int

Description:

Upgrading google-online-accounts and libgoa to 3.52.4-1 makes Google account unusable. Trying create a new one with gnome-online-accounts-gtk, logging to and opening the link with /usr/lib/goa-oauth2-handler results in error:

[20492:20492:0316/134207.172374:ERROR:atom_cache.cc(230)] Add chromium/x-internal-source-rfh-token to kAtomsToCache

(gnome-online-accounts-gtk:20309): GLib-GIO-CRITICAL **: 13:42:22.521: g_task_return_error_if_cancelled: assertion '!task->ever_returned' failed

** (gnome-online-accounts-gtk:20309): WARNING **: 13:42:22.523: Problem adding an account: Error getting an Access Token: Bad Request

Please, note: Consider holding the packages to their previous versions, because this functionality is completely broken, even though the upstream issue is already created.

Additional info:

Steps to reproduce:

  1. Start gnome-online-accounts-gtk (or gnome-online-accounts)
  2. Create a link to an account for Google account provider
  3. Give all permissions to GNOME app
  4. Open a confirmation link with a local OAuth2 handler app - normally it's /usr/lib/goa-oauth2-handler
  5. No new link to the Google account is created, the error is printed/shown instead: "Error getting an Access Token: Bad Request"
Edited by Stanislav T
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information