Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Chromium sync bug on Debian 11

Graphical Environments, Managers, Multimedia & Desktop questions.
Post Reply
Message
Author
interlagos69
Posts: 3
Joined: 2021-08-26 11:32
Has thanked: 2 times

Chromium sync bug on Debian 11

#1 Post by interlagos69 »

Hi,
I just installed Debian 11 and it works well.
But ther is a sync bug in Chromium.
Can I hope it to be fixed or it will last all during all the next two years ?
Thanks for your help.
Charles.

arzgi
Posts: 1185
Joined: 2008-02-21 17:03
Location: Finland
Been thanked: 31 times

Re: Chromium sync bug on Debian 11

#2 Post by arzgi »

No one can help you, if you don't tell anything else than 'sync bug'.

What did you try to do, did you get any error messages.

If that bug is already filed, search it, maybe someone has made a workaround.

Stable Debian gets only security updates.

arochester
Emeritus
Emeritus
Posts: 2435
Joined: 2010-12-07 19:55
Has thanked: 14 times
Been thanked: 54 times

Re: Chromium sync bug on Debian 11

#3 Post by arochester »

Google decided that they don't want people to have all the qualities of Google Chrome in e.g Chromium.

Google Chrome will sync and all of the extensions etc will work. Chromium may not.

It's not a Bug. It's Google's fault...

User avatar
craigevil
Posts: 5391
Joined: 2006-09-17 03:17
Location: heaven
Has thanked: 28 times
Been thanked: 39 times

Re: Chromium sync bug on Debian 11

#4 Post by craigevil »

Google removed sync from Chromium back in March.

https://www.omgubuntu.co.uk/2021/01/chr ... pi-removed

You can jump thru some hoops to enable it again:
1. Go to https://www.chromium.org/developers/how-tos/api-keys and follow the instructions to join the groups (https://groups.google.com/u/0/a/chromiu ... unts?pli=1 and https://groups.google.com/a/chromium.or ... romium-dev) and such in order to enable all APIs with "chrome" in their name, and to generate a:
- API key
- OAuth client id
- OAuth client secret

2. nano ~/.profile, then paste in the following:

env GOOGLE_API_KEY="API_key"
env GOOGLE_DEFAULT_CLIENT_ID="client_id"
env GOOGLE_DEFAULT_CLIENT_SECRET="client_secret"

Replace all the fields with your credentials you generated.

Run ctrl+o then ctrl+x, then press y and enter to exit nano.

3. Just logout, then log back into your account. Run Chromium and sign in to enable sync.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB
Debian - "If you can't apt install something, it isn't useful or doesn't exist"
My Giant Sources.list

interlagos69
Posts: 3
Joined: 2021-08-26 11:32
Has thanked: 2 times

Re: Chromium sync bug on Debian 11

#5 Post by interlagos69 »

Thanks for your help !
I tried to do your tuto, but it's too complicated.
It's a shame that Firefox is so slow because I could use it.
I think I'm going to let it like that.
Thanks again guy :-)
++

User avatar
salclem2
Posts: 3
Joined: 2022-03-30 14:06

Re: Chromium sync bug on Debian 11

#6 Post by salclem2 »

interlagos69 wrote: 2021-08-29 11:00 Thanks for your help !
I tried to do your tuto, but it's too complicated.
It's a shame that Firefox is so slow because I could use it.
I think I'm going to let it like that.
Thanks again guy :-)
++
1) Change this file, replacing with the created values in that procedure:
/etc/chromium.d/apikeys
# API keys assigned to Debian by Google for access to their services like sync and gmail.

export GOOGLE_API_KEY="Api_key"
export GOOGLE_DEFAULT_CLIENT_ID="client_ID"
export GOOGLE_DEFAULT_CLIENT_SECRET="client_secret"

Api_key= AIzaSyDSwqkAe0AgL9XpLS1s0xX_lTjqGHv9knY
client_ID= 838675859296-apu9s833e08s4tj2oo5sbihstnlgpkpc.apps.googleusercontent.com
client_secret= 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

2) Delete the Chromium profile in $HOME/.config

3) Restart Chromium and enable sync option

Shamak
Posts: 147
Joined: 2018-04-14 00:33
Has thanked: 11 times
Been thanked: 8 times

Re: Chromium sync bug on Debian 11

#7 Post by Shamak »

craigevil wrote: 2021-08-26 15:16 Google removed sync from Chromium back in March.

https://www.omgubuntu.co.uk/2021/01/chr ... pi-removed

You can jump thru some hoops to enable it again:
1. Go to https://www.chromium.org/developers/how-tos/api-keys and follow the instructions to join the groups (https://groups.google.com/u/0/a/chromiu ... unts?pli=1 and https://groups.google.com/a/chromium.or ... romium-dev) and such in order to enable all APIs with "chrome" in their name, and to generate a:
- API key
- OAuth client id
- OAuth client secret

2. nano ~/.profile, then paste in the following:

env GOOGLE_API_KEY="API_key"
env GOOGLE_DEFAULT_CLIENT_ID="client_id"
env GOOGLE_DEFAULT_CLIENT_SECRET="client_secret"

Replace all the fields with your credentials you generated.

Run ctrl+o then ctrl+x, then press y and enter to exit nano.

3. Just logout, then log back into your account. Run Chromium and sign in to enable sync.
I was trying this a few months ago and came across that requirement to sign up for a test account. I figured that Google would know that my account was not really a test account and nix me so I stopped there. Do you think this is true? Or can anyone just sign up?

Shamak
Posts: 147
Joined: 2018-04-14 00:33
Has thanked: 11 times
Been thanked: 8 times

Re: Chromium sync bug on Debian 11

#8 Post by Shamak »

craigevil wrote: 2021-08-26 15:16 Google removed sync from Chromium back in March.

https://www.omgubuntu.co.uk/2021/01/chr ... pi-removed

You can jump thru some hoops to enable it again:
1. Go to https://www.chromium.org/developers/how-tos/api-keys and follow the instructions to join the groups (https://groups.google.com/u/0/a/chromiu ... unts?pli=1 and https://groups.google.com/a/chromium.or ... romium-dev) and such in order to enable all APIs with "chrome" in their name, and to generate a:
- API key
- OAuth client id
- OAuth client secret

2. nano ~/.profile, then paste in the following:

env GOOGLE_API_KEY="API_key"
env GOOGLE_DEFAULT_CLIENT_ID="client_id"
env GOOGLE_DEFAULT_CLIENT_SECRET="client_secret"

Replace all the fields with your credentials you generated.

Run ctrl+o then ctrl+x, then press y and enter to exit nano.

3. Just logout, then log back into your account. Run Chromium and sign in to enable sync.
I successfully enabled sync on Chromium. I joined the two groups mentioned and followed the instructions in the link quoted above
https://www.chromium.org/developers/how-tos/api-keys

(except I only enabled the Chrome Sync API) but did not have to create the credentials (API key, client id, client secret). I got to that point and decided to just try it to see if I could at least sign in to Chromium. I restarted the computer, signed in to Chromium, and sync was enabled. Perhaps the Debian credentials are still valid if one signs up for the groups.
Last edited by Shamak on 2022-04-20 14:24, edited 5 times in total.

Shamak
Posts: 147
Joined: 2018-04-14 00:33
Has thanked: 11 times
Been thanked: 8 times

Re: Chromium sync bug on Debian 11

#9 Post by Shamak »

Shamak wrote: 2022-03-30 21:34 I was trying this a few months ago and came across that requirement to sign up for a test account. I figured that Google would know that my account was not really a test account and nix me so I stopped there. Do you think this is true? Or can anyone just sign up?
I came across this github conversation where person after person was saying that the procedure had worked for them. No one had come back on saying that Google had nixed their accounts so I don't think there's a problem.

https://gist.github.com/cvan/44a6d60457 ... b104f9dcc4

User avatar
craigevil
Posts: 5391
Joined: 2006-09-17 03:17
Location: heaven
Has thanked: 28 times
Been thanked: 39 times

Re: Chromium sync bug on Debian 11

#10 Post by craigevil »

Google could care less if individuals use sync. It was other browsers that were using it that made them remove it.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB
Debian - "If you can't apt install something, it isn't useful or doesn't exist"
My Giant Sources.list

Shamak
Posts: 147
Joined: 2018-04-14 00:33
Has thanked: 11 times
Been thanked: 8 times

Re: Chromium sync bug on Debian 11

#11 Post by Shamak »

craigevil wrote: 2021-08-26 15:16 Google removed sync from Chromium back in March.

https://www.omgubuntu.co.uk/2021/01/chr ... pi-removed

You can jump thru some hoops to enable it again:
1. Go to https://www.chromium.org/developers/how-tos/api-keys and follow the instructions to join the groups (https://groups.google.com/u/0/a/chromiu ... unts?pli=1 and https://groups.google.com/a/chromium.or ... romium-dev) and such in order to enable all APIs with "chrome" in their name, and to generate a:
- API key
- OAuth client id
- OAuth client secret

2. nano ~/.profile, then paste in the following:

env GOOGLE_API_KEY="API_key"
env GOOGLE_DEFAULT_CLIENT_ID="client_id"
env GOOGLE_DEFAULT_CLIENT_SECRET="client_secret"

Replace all the fields with your credentials you generated.

Run ctrl+o then ctrl+x, then press y and enter to exit nano.

3. Just logout, then log back into your account. Run Chromium and sign in to enable sync.
It seems you just have to join the two groups quoted above and sync will work. I disabled the chrome sync api that I had enabled and sync is still working. (And I'm guessing that's because I was using Debian's credentials all along and not my own.)

Post Reply