#1067441 chromium: Unable to sync profile

Package:
chromium
Source:
chromium
Description:
web browser
Submitter:
Wesley Schwengle
Date:
2025-10-20 03:05:03 UTC
Severity:
normal
#1067441#5
Date:
2024-03-21 16:11:30 UTC
From:
To:
Dear Maintainer,

I've started up Chromium and want to sync my Google account.

* Create new profile
* Login to Google (succesfully)
  Within Google.com you are known, myaccount.google.com shows your details
* Click on the profile button of your browser
* Clock on "Turn sync on"
* Follow the login sequence
* Notice error in the console:

[29150:29150:0321/112903.702701:ERROR:turn_sync_on_helper.cc(256)] Cannot turn Sync On for invalid account.
[29150:29150:0321/112950.431580:ERROR:turn_sync_on_helper.cc(256)] Cannot turn Sync On for invalid account.

Doing the same action with the builds of Google itself everything works fine,
tested this with the browsers listed below.

The bug is also present on bookworm, where I tested it with 122.0.6261.128-1~deb12u1

Cheers,
Wesley


google-chrome-stable:
  Installed: 123.0.6312.58-1
  Candidate: 123.0.6312.58-1
  Version table:
 *** 123.0.6312.58-1 900
        900 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages
        100 /var/lib/dpkg/status
google-chrome-beta:
  Installed: 123.0.6312.46-1
  Candidate: 123.0.6312.46-1
  Version table:
 *** 123.0.6312.46-1 900
        900 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages
        100 /var/lib/dpkg/status
google-chrome-unstable:
  Installed: 124.0.6356.2-1
  Candidate: 124.0.6356.2-1
  Version table:
 *** 124.0.6356.2-1 900
        900 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages
        100 /var/lib/dpkg/status
#1067441#10
Date:
2024-07-29 08:09:12 UTC
From:
To:
Dear Maintainer,

it is possible to go around this bug by starting chromium with these arguments:
#1067441#13
Date:
2024-07-31 04:02:45 UTC
From:
To:

Do you know if this worked proper with chromium 121 or earlier?
#1067441#18
Date:
2024-07-31 14:34:43 UTC
From:
To:
I'm do not. If there is a deb floating around we can probably check that.
#1067441#21
Date:
2024-07-31 14:34:43 UTC
From:
To:
I'm do not. If there is a deb floating around we can probably check that.
#1067441#26
Date:
2025-10-20 03:03:35 UTC
From:
To:
It seems that the google api key debian is using at
/etc/chromium.d/apikeys is out of date. I can't sign in google account
recently. After changing the keys in the file I can sign into my account:

#export GOOGLE_API_KEY="AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k"
#export GOOGLE_DEFAULT_CLIENT_ID="811574891467.apps.googleusercontent.com"
#export GOOGLE_DEFAULT_CLIENT_SECRET="kdloedMFGdGla2P1zacGjAQh"
export GOOGLE_DEFAULT_CLIENT_ID="77185425430.apps.googleusercontent.com"
export GOOGLE_DEFAULT_CLIENT_SECRET="OTJgUOQcT7lO7GsGZq2G4IlT"


The old keys may get denied for some reason since it was added at 2014.
Maybe we can update a new working api key sets for debian package.

Best regards,

Jianfeng