Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

spotify: error while loading shared libraries: libgcrypt.so.11

Solved!

spotify: error while loading shared libraries: libgcrypt.so.11

$ spotify
spotify: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory

$

 

A recent update depends on libgcrypt11 but debian only has libgcrypt20. Is there a solution to this? Or can I revert somehow?

 

I am currently running:

  • debian jessie/sid
  • kernel 3.16-3-amd64

 

Thank you.

Reply

Accepted Solutions
Marked as solution

Thank you for the reply.

 

I came up with a similar solution: I downloaded the libgcrypt11 library for Debian Wheezy and installed it via

 

~# dpkg -i libgcrypt11_1.5.0-5+deb7u1_amd64.deb

Now Spotify works again. However, this should only be treated as a temporary solution, as the upcoming Debian release Jessie will not ship the old version of the library and it generally not a good approach to manually install packages from another (and soon outdated) release.

View solution in original post

Marked as solution

The new version mentioned above works great! Thanks, MarcosC for linking the new package.

 

For those wishing to make the switch, you can try the following.

 

 

sudo apt-get purge spotify-client
sudo apt-get autoremove
sudo add-apt-repository --remove 'deb http://repository.spotify.com stable non-free'
sudo apt-get update wget http://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.7.153.gb9e8174a_amd64.deb sudo dpkg -i spotify-client_1.0.7.153.gb9e8174a_amd64.deb spotify &

You're also definitely going to want to get rid of libgcrypt11_1.5.0 unless you wish to enjoy being potentially vulnerable to attacks described here: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-5270

 

View solution in original post

Marked as solution

Finally some movement!

 

Thanks for the update MarcosC

 

equaint:

 

Apt repositories exist so you can upgrade your installed software when there is an upgrade path available - without doing any manual steps (other than the upgrade call). This isn't windows. Learn to use your distribution package manager!

just edit your /etc/apt/sources.list from stable to testing

remove the app, then install it with apt-get install spotify-client.

It should even work with apt-get upgrade without removing it but I didn't try it since I had it uninstalled already.

Works without libgcrypt11 though the app only works in fullscreen mode for me. No windowing, or menus for it either. still better though than running unsafe libs 🙂

View solution in original post

Marked as solution

It is missing the echo command. The correct sequence of commands is

 

sudo apt-get purge spotify-client
sudo apt-get autoremove
sudo add-apt-repository --remove 'deb http://repository.spotify.com stable non-free'
sudo echo deb http://repository.spotify.com testing non-free | sudo tee /etc/apt/sources.list.d/spotify.list
sudo apt-get update
sudo apt-get install spotify-client

 

Thank you again to Asile for found this solution! it works!

 

View solution in original post

53 Replies

It might be worth creating a symbolic link from one library to the other and see if that works?

Peter
Spotify Community Mentor and Troubleshooter

Spotify Last.FM Twitter LinkedIn Meet Peter Rock Star Jam 2014


If this post was helpful, please add kudos below!

Same problem here. I tried creating a symbolic link to the new lib version. This ist the result when trying to start Spotify:

 

spotify: /lib/x86_64-linux-gnu/libgcrypt.so.11: version `GCRYPT_1.2' not found (required by /opt/spotify/spotify-client/Data/libcef.so)

 

I remember I came across this problem on Arch a while ago, and was able to solve it using an older package provided by in AUR the community.

If I were you I would try to compile the same version the latest Ubuntu uses, which is version 1.5.4. Don't confuse by the package version vs the lib version. Version 1.5.4 provides libgcrypt11.

You can find it here:

ftp://ftp.gnupg.org/gcrypt/libgcrypt/

Or you could try copying the file from Ubuntu. According to this the package only provides one file (of importance). You can download it and extract it and put the file in the correct location.

http://packages.ubuntu.com/utopic/libgcrypt11

I'm writing on my phone so sorry if it's a bit messy.
SpotCommander - The most elegant, intuitive, feature-rich & universal remote control for Spotify, exclusive for Linux users!

BTW you'll probably have to run "sudo ldconfig" after placing the file.
SpotCommander - The most elegant, intuitive, feature-rich & universal remote control for Spotify, exclusive for Linux users!
Marked as solution

Thank you for the reply.

 

I came up with a similar solution: I downloaded the libgcrypt11 library for Debian Wheezy and installed it via

 

~# dpkg -i libgcrypt11_1.5.0-5+deb7u1_amd64.deb

Now Spotify works again. However, this should only be treated as a temporary solution, as the upcoming Debian release Jessie will not ship the old version of the library and it generally not a good approach to manually install packages from another (and soon outdated) release.

Great. The devs have clearly stated that they only support Ubuntu, despite the download page saying Debian. Since Debian is Ubuntu based I'm sure it'll be fixes sooner or later. The upcoming v 1.0, maybe.
SpotCommander - The most elegant, intuitive, feature-rich & universal remote control for Spotify, exclusive for Linux users!

Actually Ubuntu is based on Debian and not the other way around.

 

I got this same libgcrypt.so.11 problem but I solved it by installing libgcrypt11 from the Debian archives.

 

On Debian libgcrypt11 is superseded with libgcrypt20 and libgcrypt11 wasn't installed on my system as it wasn't required by any other package.

 

Spotify should add libgcrypt11 as a required dependency or migrate to ibgcrypt20.


@olejon wrote:
Great. The devs have clearly stated that they only support Ubuntu, despite the download page saying Debian. Since Debian is Ubuntu based I'm sure it'll be fixes sooner or later. The upcoming v 1.0, maybe.

Well, it's now borken in Ubuntu 15.04 too, so doubtless someone at Spotify will get their finger out and start depending on libgcrypt20 instead.

 

Downloading and installing Debian Wheezy's libgcrypt11 works as a temporary fix here (and stops the tears that would have happened when my daughter got back from school and found Spotify wouldn't work...)

That worked for me on Ubuntu 15.04. Thanks!

libgcrypt11 won't be included in Jessie: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784054

I hope Spotify plans to upgrade to libgcrypt20.

Here's hoping this would be resolved in the near future - using workarounds for now.

Dear Spotify dev team, now that Ubuntu 15.04 is out, you have to update your dependencies if you don't want to make this post flooded...

I had to use the workaround too.

Confirming that I had to deal with this too. Spotify please.

Just upgraded to 15.04, confirmed that this is still an issue and the fix of downloading and installing the wheezy libgcrypt1.1 worked for me.

I already dealed with this anoying issue downloading the debian install file at

 

https://packages.debian.org/wheezy/amd64/libgcrypt11/download

 

then just installing it from terminal with this

 

dpkg -i libgcrypt11_1.5.0-5+deb7u1_amd64.deb

 

 

Also had to manually install the debian package on xubuntu 15.04 to get spotify working again Smiley Mad

I'm running Debian Jessie, and libgcrypt11 is no longer available in the repos. The following worked perfectly for me, based on yafuslae's link above. First, download the legacy libgcrypt11 package (via the web):

 

http://security.debian.org/debian-security/pool/updates/main/libg/libgcrypt11/libgcrypt11_1.5.0-5+de...

 

Then install with:

 

sudo dpkg -i libgcrypt11_1.5.0-5+deb7u3_amd64.deb

This is not a great solution, since there is a potential for shared object conflict now.

 

Unnecessary trivia: the first answer, to try a symbolic link libgcrypt.so.11 -> libgcrypt.so was the first thing I tried, but it doesn't work because the object name (SONAME) is embedded in the object file, as revealed by:

 

objdump -p /lib/x86_64-linux-gnu/libgcrypt.so.20.0.3 | grep SONAME

 

This is not a solution. This is a bloody hack. Why would you recommend people to install deprecated deb packages?

A good reason for not installing such things: https://lists.debian.org/debian-security-announce/2014/msg00262.html

Would be interesting to know why Spotify still uses libgcrypt 11 instead of 20

Suggested posts