New issue
Advanced search Search tips

Issue 107334 link

Starred by 18 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jun 2012
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment

Bad signature encountered on update

Reported by mrjohnlu...@gmail.com, Dec 13 2011

Issue description

Chrome Version       : 16.0.912.63 beta
OS Version: Ubuntu 10.04 LTS
URLs (if applicable) : N/A
Other browsers tested: N/A
  
What steps will reproduce the problem?
1.Run Ubuntu Update Manager
.

What is the expected result?

 Check for and apply program updates

What happens instead?

 Failure message (see below)

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

Failure message:

W: GPG error: http://dl.google.com stable Release: The following signatures were invalid: BADSIG A040830F7FAC5991 Google, Inc. Linux Package Signing Key <linux-packages-keymaster@google.com>

Tried re-installing Google Chrome (both stable and beta) with no change.

 

Comment 1 by fyresp...@gmail.com, Dec 13 2011

Seeing this when trying to update chrome on my Debian Wheezy install:

Reading package lists... Done
W: A 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 stable Release: The following signatures were invalid: BADSIG A040830F7FAC5991 Google, Inc. Linux Package Signing Key <linux-packages-keymaster@google.com>

W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release  

I tried removing the key, downloading it and reinstalling it and downloading the chrome package again and installing it.  neither worked.

The fix for me was to modify my apt repo using:

sudo vi /etc/apt/sources.list.d/google-chrome.list

I changed it from:

deb http://dl.google.com/linux/chrome/deb/ stable main

to:

deb http://dl.google.com/linux/deb/ stable main

This fixed it for me.

Looks like chrome the chrome update/install isn't updating the repo in the repo list correctly

Comment 2 by molost...@gmail.com, Dec 13 2011

The same with my Ubuntu Oneiric and Google Chrome 17.0.963.2 dev
Amazing. Months later, on Ubuntu 12.04 LTS plus Chrome version 18.0.1025.162, and this is still the case. Both issue and fix.

Thanks for sharing :)

Comment 4 by Deleted ...@, Apr 30 2012

Same for me right now. Ubuntu 12.04 LTS Chrome Version 20.0.1115.1 dev 

Comment 5 by Deleted ...@, Jun 14 2012

Same for me. Ubuntu 12.04 LTS Chrome Version 19.0.1084.56

Comment 6 by p...@pjbrunet.com, Jun 14 2012

The "deb http://dl.google.com/linux/deb/ stable main" solution worked for me but I had to run apt-get update twice as per the following error message suggestion...

"W: Duplicate sources.list entry http://dl.google.com/linux/deb/ stable/main i386 Packages (/var/lib/apt/lists/dl.google.com_linux_deb_dists_stable_main_binary-i386_Packages)
W: You may want to run apt-get update to correct these problems"

PS: I'm on Debian 6.0.5

Comment 7 Deleted

Comment 8 by Deleted ...@, Jun 14 2012

The "deb http://dl.google.com/linux/deb/ stable main" solution worked for me... didn't need to run apt-get update twice.

Linux Mint 13  Chrome Version 19.0.1084.56-r140965
I'm getting this today also. Changing the deb line is not a fix because that is a different repo which doesn't even host google-chrome packages (well it has ancient versions of stable and unstable, no beta).

Comment 10 by Deleted ...@, Jun 14 2012

http://forums.debian.net/viewtopic.php?f=10&t=80717

quote:
"its a known bug the work around for now is to change the repo

The correct line for now needs to be:
deb http://dl.google.com/linux/chrome_testing/deb/ stable main


Note the change is the /chrome_testing/ part"

Well, It stopped bothering.


Comment 11 by Deleted ...@, Jun 14 2012

Thanks, is working for me. Ubuntu 10.04 LTS and Chrome Version 19.0.1084.56
Status: Fixed
There was a bad push yesterday that caused the GPG error. It's been fixed. Bad pushes happen from time to time unfortunately.
Project Member

Comment 13 by bugdroid1@chromium.org, Oct 13 2012

Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member

Comment 14 by bugdroid1@chromium.org, Mar 11 2013

Labels: -Area-Undefined

Sign in to add a comment