Repository Update Problem - Google Earth <Solved>

[fstjohn]

When the Update Manager refresh takes place I get the following error:
Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://dl.google.com/linux/earth/deb stable InRelease' doesn't support architecture 'i386'Repository 'http://dl.google.com/linux/chrome/deb stable Release' changed its 'Origin' value from 'Google, Inc.' to 'Google LLC'

This is a new error. Mint Cinnamon 19, 64bit
How can I fix this?

[AndyMH]

Just got that one myself. Goto menu > admin > software sources > additional repositories and remove the one for google earth (be careful, if you have chrome installed there will be two google entries).

[g1230g]

Just got that one myself. Goto menu > admin > software sources > additional repositories and remove the one for google earth (be careful, if you have chrome installed there will be two google entries).

I am getting the same thing. I am using Google Chrome and am only seeing one Google repository not two...any thoughts?

[AndyMH]

Having deleted the repo for google earth I'm now getting:

Repository 'http://dl.google.com/linux/chrome/deb stable Release' changed its 'Origin' value from 'Google, Inc.' to 'Google LLC'

So I shall probably delete that as well.

[fstjohn]

Looks like Google has made a change to its repository. Hopefully they'll fix it in time, or make an announcement how to fix it on this end.

[MrEen]

I just installed Chrome and here's the repo I ended up with: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main

[LanceM]

This fixed mine. Open the update manager>edit>software sources>maintenance>click fix mergelist problems. mine said fixed. Then you reload the cache and click ok.
done.
hope this helps you!

[fstjohn]

"This fixed mine. Open the update manager>edit>software sources>maintenance>click fix mergelist problems. mine said fixed. Then you reload the cache and click ok.
done.
hope this helps you!"

Thanks! This fixed the problem. I"ll remember it for future problems.

[Pjotr]

But do you still get updates for your Google stuff then, or has the Google repo simply been removed by your action (thus essentially leaving you in the cold with no security updates for all things Google)?

[missmoondog]

This fixed mine. Open the update manager>edit>software sources>maintenance>click fix mergelist problems. mine said fixed. Then you reload the cache and click ok.
done.
hope this helps you!

thank you. just came up with this issue too!!

all fixed!

[Pjotr]

This should give you the option to explicitly accept the name change:

Code: Select all

sudo apt update

[trytip]

what Pjotr said +1
anyone getting a google error must run apt update in Terminal to ACCEPT the new name change after which the error is gone

[DAMIEN1307]

this also effects the "brave browser" which also uses the dl.google.com main...both trytip and pjotr mentioned to use the apt update...that is the way to go...

Code: Select all

sudo apt update 

yesterday morning when i noticed the update manager wasnt working and that corrected the problem.

[Ceilidh2]

Worked for me.

Thank you Pjotr.

[xavier777]

This should give you the option to explicitly accept the name change:

Code: Select all

sudo apt update

yes it works now. thanks

[deanr72]

Hi.

Just had the same issue with Chrome on Mint Cinnamon 19. After removing Chrome from additional repositories, updating cache and running sudo apt update the only entry I have for Google now is under the Authentication keys tab.

So now I have the same concern as a previous poster - am I actually getting updates to Chrome when I run Update Manager? It says everything is up-to-date but it didn't download anything extra after the initial error message and updating everything else.

Thanks,

[Pjotr]

Hi.

Just had the same issue with Chrome on Mint Cinnamon 19. After removing Chrome from additional repositories, updating cache and running sudo apt update the only entry I have for Google now is under the Authentication keys tab.

So now I have the same concern as a previous poster - am I actually getting updates to Chrome when I run Update Manager?

No, of course not.

[MrEen]

Hi.

Just had the same issue with Chrome on Mint Cinnamon 19. After removing Chrome from additional repositories, updating cache and running sudo apt update the only entry I have for Google now is under the Authentication keys tab.

So now I have the same concern as a previous poster - am I actually getting updates to Chrome when I run Update Manager? It says everything is up-to-date but it didn't download anything extra after the initial error message and updating everything else.

Thanks,

Hi deanr72. What you should have done is just the running of apt update as Pjotr stated earlier in the thread so you could accept the change for google. If you only unchecked the box for the Chrome repo, just recheck it then run apt update in the terminal, accept the change, and all will be good. I can't safely help if you fully removed the repo I'm afraid, but I'm sure others will be able to assist.

[Pjotr]

You can re-install the .deb installer for Chrome, in order to add its repo again.

[deanr72]

Thanks, I'll try the deb. installer first then perhaps a fresh install of chrome.

I'm working in another country for the next 10 days though so I won't risk anything till I'm back home...