Welcome to SparkyLinux forums
Zapraszamy również na polsko-języczne Forum https://forum.linuxiarze.pl

[ Solved ] Failed to fetch - Hash Sum mismatch

Started by way12go, December 10, 2014, 03:28:56 AM

Previous topic - Next topic

way12go

Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/main/binary-i386/Packages  Hash Sum mismatch

sudo rm -rf /var/lib/apt/lists/*


sudo apt-get update

Fetched 19.5 MB in 44s (435 kB/s)                                             
Reading package lists... Done
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>


http://www.ubuntugeek.com/how-to-fix-the-ubuntu-gpg-error-badsig.html

Error Message

W: GPG error: http://archive.canonical.com intrepid Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key

Method 1

Try to run the following comamnds from terminal

    $ sudo -i

    # apt-get clean

    # cd /var/lib/apt

    # mv lists lists.old

    # mkdir -p lists/partial

    # apt-get clean

    # apt-get update


Fetched 19.5 MB in 24s (801 kB/s)                                             
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/main/binary-i386/Packages  Hash Sum mismatch

E: Some index files failed to download. They have been ignored, or old ones used instead.


Method 2

Try to run the following comamnds from terminal

    sudo aptitude -o Acquire::http::No-Cache=True -o Acquire::BrokenProxy=true update

    sudo apt-get update


Fetched 70.7 kB in 10s (6,726 B/s)                                             
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 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:
W: Some index files failed to download. They have been ignored, or old ones used instead.


Then used Sparky-aptus and then tried synaptic package manager

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 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 

W: Some index files failed to download. They have been ignored, or old ones used instead.


Solution:

Few minutes ago when I updated package list and clicked on update Synaptic package manager updated google chrome. I installed google chrome deb file from google website yesterday night and then after todays update I keep getting the above problems.

What I did is I went sparky-aptus and edited

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

Added # to the above deb code and the problem was no longer there.

Now, the problem is, how do I update google chrome in the future if this deb code is disabled?
Success gives birth to success? Failure gives birth to failure? - Sagar Gorijala.

way12go

Solution:

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

https://sites.google.com/site/mydebiansourceslist/

http://www.google.com/linuxrepositories/

I did this command and the problem got solved.

SOLUTION:

wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
Success gives birth to success? Failure gives birth to failure? - Sagar Gorijala.

GeneC

#2
I checked earlier today and found this same issue.. :(
QuoteFailed to fetch - Hash Sum mismatch

However the issue appears to have been fixed in the repo and is no longer there, and google-chrome updated just now with no issues, and having to make no adjustments...
Start-Date: 2014-12-10  09:03:36
Commandline: /usr/sbin/synaptic
Upgrade: google-chrome-stable:amd64 (39.0.2171.71-1, 39.0.2171.95-1)
End-Date: 2014-12-10  09:03:46
GeneC

rmaijala

hi, when i recently tried upgrading some packages i got the following error message similar to the one for google chrome


Failed to fetch xz:/var/lib/apt/lists/partial/ftp.debian.org_debian_dists_testing_main_binary-i386_Packages  Hash Sum mismatch
Some index files failed to download. They have been ignored, or old ones used instead.


this came from synaptic when trying to upgrade lxpanel
similar results yesterday when trying to upgrade "all" via synaptic and apt-get.
any suggestions?

way12go

http://forums.debian.net/viewtopic.php?f=10&t=61493#p358341

QuoteI've seen that before, too.

My understanding is that it happens when you try to do an update while the repository itself is in the process of being updated.

Whenever I see that error, I wait an hour or two and then try again, and everything is fine.

404 error

http://makululinux.webs.com/apps/forums/topics/show/12479100

Quote404 means those repositories are down. debian repo's sometimes do go down, they can be down for few minutes or few hours, I am sure they are working on the problem right now.

However you can change the mirrors if you do not wish to wait.

in terminal type :

    su
    nano /etc/apt/sources.list

and then everywhere where it says :

    deb http://us.debian.org xxxxxxxxxx


change it to

    deb http://ftp.debian.org/ xxxxxxxxxx

Change just the front part of the url and leave the rest as is.

Then press CTRL+X button to close, Y button to save and overwrite.

then do apt-get update again.

Try to run the following comamnds from terminal

    $ sudo -i

    # apt-get clean

    # cd /var/lib/apt

    # mv lists lists.old

    # mkdir -p lists/partial

    # apt-get clean

    # apt-get update
Success gives birth to success? Failure gives birth to failure? - Sagar Gorijala.

rmaijala

^^^ Yeah it seems to be online now. I found it odd that it was down yesterday during the day and then this morning again. The hash sum mismatch is a strange error message.

View the most recent posts on the forum