New issue
Advanced search Search tips

Issue 752813 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 0
Type: Bug



Sign in to add a comment

ubuntu installer is hosed due to public key check

Reported by jda...@pcprogramming.com, Aug 6 2017

Issue description

Chrome Version       : latest
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
         IE:

What steps will reproduce the problem?
(1) install or update chrome on ubuntu
(2)
(3)

What is the expected result?
no errors

What happens instead?
errors

Please provide any additional information below. Attach a screenshot if
possible.

Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Get:2 http://dl.google.com/linux/chrome/deb stable Release [1,189 B]           
Get:3 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B]         
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial InRelease                     
Err:3 http://dl.google.com/linux/chrome/deb stable Release.gpg                 
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E
Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]     
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]  
Fetched 307 kB in 0s (445 kB/s)                                                
Reading package lists... Done
W: 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 couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E
W: Some index files failed to download. They have been ignored, or old ones used instead.

 

Comment 1 by mmoss@chromium.org, Aug 7 2017

Cc: thestig@chromium.org waff...@chromium.org
Components: Internals>Installer
Labels: -Pri-3 OS-Linux Pri-0
Owner: mmoss@chromium.org
Status: Assigned (was: Unconfirmed)
This was caused by prematurely trying to dual-sign with a new key (the "2017" key) which isn't widely distributed yet. The repository is being resigned with just the older ("2016") key and should be updated shortly.
The repository should be fixed now.

Comment 3 by mmoss@chromium.org, Aug 7 2017

Hmm, I'm still showing it signed with 997C215E, but it should be 640DB551. Looking.

Comment 4 by mmoss@chromium.org, Aug 7 2017

Status: Fixed (was: Assigned)
I'm now seeing the expected key:

gpg: Signature made Mon 07 Aug 2017 09:44:58 AM PDT using RSA key ID 640DB551

so this should be fixed. Please respond if you're still seeing any errors.

Sign in to add a comment