Purchase Linux CDs / DVDs / Flash Drives at OSDisc.com

Welcome to Our Community

While Linux.org has been around for a while, we recently changed management and had to purge most of the content (including users). If you signed up before April 23rd, 2017 please sign up again. Thanks!

  1. More ways to get the info! - we shoot all of our new original content out as well as random messages on Twitter and our newsletter!. Twitter | Newsletter
    Dismiss Notice

Error Message Linux 19.1

Discussion in 'Mint' started by Madmick70, Apr 12, 2019.

  1. Madmick70

    Madmick70 New Member

    Joined:
    Jun 18, 2018
    Messages:
    8
    Likes Received:
    3
    An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <[email protected]>Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg 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.


    (Log in to hide this advertisement)


    How do i fix
     
  2. Condobloke

    Condobloke Well-Known Member

    Joined:
    Apr 30, 2017
    Messages:
    725
    Likes Received:
    737
    G'day Mick, do you use Chrome browser ?

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

    Madmick70 New Member

    Joined:
    Jun 18, 2018
    Messages:
    8
    Likes Received:
    3
    Afternoon here and yes i do use Google Chrome browser
     
  4. Condobloke

    Condobloke Well-Known Member

    Joined:
    Apr 30, 2017
    Messages:
    725
    Likes Received:
    737
    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.
     
    wizardfromoz likes this.
  5. JasKinasis

    JasKinasis Well-Known Member

    Joined:
    Apr 25, 2017
    Messages:
    367
    Likes Received:
    688
    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:
    https://support.google.com/chrome/thread/4032170?hl=en

    https://askubuntu.com/questions/113...tures-were-invalid-expkeysig-1397bc53640db551

    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.
     
    wizardfromoz and Condobloke like this.
  6. Mjv4L

    Mjv4L New Member

    Joined:
    Apr 12, 2019
    Messages:
    1
    Likes Received:
    0
  7. Madmick70

    Madmick70 New Member

    Joined:
    Jun 18, 2018
    Messages:
    8
    Likes Received:
    3
  8. JasKinasis

    JasKinasis Well-Known Member

    Joined:
    Apr 25, 2017
    Messages:
    367
    Likes Received:
    688
    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 google.com - 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!
     
    Condobloke likes this.

Share This Page