Error Message Linux 19.1


New Member
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: stable Release: The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <[email protected]>Failed to fetch The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <[email protected]>Some index files failed to download. They have been ignored, or old ones used instead.

How do i fix


Well-Known Member
G'day Mick, do you use Chrome browser ?

(I received a similar error on my wife's pc tonight)


Well-Known Member
I think this may be widespread. Others may be able to confirm that.

(On my wife's pc i simply deleted the google chrome repository entry in Additional Repositoreies which is found in Software Sources in the update manager)

I deleted it because she does not use Chrome browser

In your case it may well be a better move to leave everything alone for a day or two....and I am quite sure the updates system will take care of it.

It will do no harm.


Well-Known Member
It looks as if there is some problem with Google's gpg key, which is used to sign their packages. Perhaps it has expired or something.

A quick bit of duckduckgo-fu more or less confirms my suspicions. This looks to be an issue at Google's end:

Maybe wait a day or so and see if there is any resolution.
Or if you can't wait - perhaps try downloading the latest .deb installer for chrome, then uninstall the current version, remove the stored keys for google and then re-install the latest chrome .deb package. That might fix the gpg key issue. On the other hand - it might be better to keep an eye on the bug reported in the first link and see if there are any answers/solutions posted there.


Well-Known Member
When I updated my laptop on Friday evening - I got the same errors about the google GPG Key.

But when I updated it again, last night - apt no longer complained about the problem. So it looks as if this issue has been more or less resolved now.

Looking at the Chrome support thread on - most of the Google repos have been re-signed using the original key, which I guess has been renewed.

There are people still complaining about the repos for one or two other pieces of google software which still need to be re-signed. But it looks as if the problem has been fixed for Chrome users on Linux!

Members online

Latest posts