Announcements
The Spotify Stars Program: Celebrating Values Week!

Help Wizard

Step 1

NEXT STEP

Unable to install on ubuntu 15.04 for hash sum mismatch

Solved!

Unable to install on ubuntu 15.04 for hash sum mismatch

Hi,

 

I just installed ubuntu 15.04, was following https://www.spotify.com/us/download/previews/ and after adding the key and the repo to sources.list apt-get says:

 

W: Failed to fetch http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages  Hash Sum mismatch

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

and apt-get install spotify-client does not find the package

 sudo apt-get install spotify-client
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package spotify-client

Any clue in how to fix this ?

Reply

Accepted Solutions
Marked as solution

I've found a solution since spotify people seems to take way more than necessary to fix their own deb repo.

 

First of all get spotify package, it is http://repository.spotify.com/pool/non-free/s/spotify/spotify-client_0.9.17.1.g9b85d43.7-1_amd64.deb

Then get libgcrypt11, it is on debian from http://security.debian.org/debian-security/pool/updates/main/libg/libgcrypt11/libgcrypt11_1.5.0-5+de...

 

Install both packages with dpkg -i package.deb or double clicking on them.

 

Whoila' you have spotify. cheers!

View solution in original post

26 Replies

I am running Ubuntu 14.04 and I have Spotify already installed. I ran:

 

sudo apt-get update

and got the same error as you:

 

W: Failed to fetch http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages  Hash Sum mismatch

W: Failed to fetch http://repository.spotify.com/dists/stable/non-free/binary-i386/Packages  Hash Sum mismatch

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

To fix this error start by running these commands, and then try to install the package again.

 

Remove the content of /var/lib/apt/lists directory:

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

Update package lists

sudo apt-get update

 

Remember that you always have to update the package lists before an installation to ensure you get the latest version of the packages you request.

 

EDIT:

This fix should work given that you have properly added the repo and the key. See below

 

Add the following line to your etc/apt/sources.list

deb http://repository.spotify.com stable non-free

Add the aproriate public key

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 94558F59
Of all the things I´ve ever lost I miss my mind the most - Ozzy Osbourne

Didn't work unfortunately. I had to run:

 

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

...but the error remains

I have the same problem. Running 

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

 

does not fix the error 

using Debian Jessie - cleaning out the lists folder solved it for me.

I have the same problem here, anyone found a solution?

 

Marked as solution

I've found a solution since spotify people seems to take way more than necessary to fix their own deb repo.

 

First of all get spotify package, it is http://repository.spotify.com/pool/non-free/s/spotify/spotify-client_0.9.17.1.g9b85d43.7-1_amd64.deb

Then get libgcrypt11, it is on debian from http://security.debian.org/debian-security/pool/updates/main/libg/libgcrypt11/libgcrypt11_1.5.0-5+de...

 

Install both packages with dpkg -i package.deb or double clicking on them.

 

Whoila' you have spotify. cheers!

Lol vampolo I was just writing a turtorial / bash script!

 

But yes, the response above is the best solution to this until Sotify updates their keys.

 

 

Currently listening to Deltron 3030 🙂

You're awesome! This works for 14.04 as well, after trying three other things, that link is the only thing that's worked.

 

Everything plays, including remotely, and it can open and close from the icon, without needing terminal open.

 

Thanks!

This worked great. Thanks.

I am now up and running as well.

 

I already had Spotify installed, but was getting the same errors. To fix, all I needed to do was to reistall the Spotify .deb package. I didn't need libgcrypt11, as I was already running a newer version.

 

thanks @vampolo.

The real problem is a mismatch between the checksum of the downloaded Packages.gz and what is in InRelease.

 

I've downloaded these files and computed md5sum

4bfa1d4da7e0d639f5682d1bcffbf671 Packages
c1b40790a4de8f07fbe221c0b9a396c5 Packages.gz

a6c45b9be906f8c19f07640f4087febd Release

 

But InRelease says:

MD5Sum:
4bfa1d4da7e0d639f5682d1bcffbf671 4409 non-free/binary-amd64/Packages
dfefc4034b6b440d9a9e3c3ebe361536 1433 non-free/binary-amd64/Packages.gz
a6c45b9be906f8c19f07640f4087febd 194 non-free/binary-amd64/Release

 

The workarounds are nice but the problem needs to be fixed by the Spotify guys.

Is one of the Spofify developers listening? Or else, how do we notify the right people? To me it seems a 5 minute job to fix this problem.

Spofify => Spotify 🙂

This only works with a 64bit machine. I have a 32bit machine running 15.04 and according to online sources there is no 32bit deb package for Spotify. I was running Spotify perfectly before on 14.10. I've exhausted all possible solutions, Spotify surely has a monopoly with Window users and forgets Linux? 🙂

Same issue here:

Xubuntu x86 - 15.04: unable to install the spotify client. For some reason the spotify repository is ignored when doing "update". 

Please have a look at this spotify!

 

I can't reproduce this.

 

$ REPO=http://repository.spotify.com/dists/stable

$ curl -s $REPO/InRelease | grep binary-amd64 | head -n3
4bfa1d4da7e0d639f5682d1bcffbf671 4409 non-free/binary-amd64/Packages
dfefc4034b6b440d9a9e3c3ebe361536 1433 non-free/binary-amd64/Packages.gz
a6c45b9be906f8c19f07640f4087febd 194 non-free/binary-amd64/Release
$ curl -s $REPO/non-free/binary-amd64/Packages | md5sum -
4bfa1d4da7e0d639f5682d1bcffbf671 -
$ curl -s $REPO/non-free/binary-amd64/Packages.gz | md5sum -
dfefc4034b6b440d9a9e3c3ebe361536 -
$ curl -s $REPO/non-free/binary-amd64/Release | md5sum -
a6c45b9be906f8c19f07640f4087febd -

 

What you describe can probably happen, but it is much more likely that it is a CDN problem and there is a broken copy of Packages.gz out there somewhere. To test the CDN theory, replace repository with repository-origin.

Strange, now I can't reproduce it anymore either.

So, yes, it could have been a CDN problem.

It has been fixed.

 

I dunno the Spotiffy architecture but if you guys didn't change package at all (which seems the case) it was probably a cdn problem that for some days it was referencing a broken Packages.gz as you said @jooon.

Suggested posts