Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
$ 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:
Thank you.
Solved! Go to Solution.
https://launchpad.net/ubuntu/+archive/primary/+files/libgcrypt11_1.5.3-2ubuntu4.2_amd64.deb
fixed it for me on 15.04 ubuntu, no dependency issues
sata,
I agree with you that it's not a solution. Other than switching to an unsupported Spotify client (e.g. mopidy)--which is also a hack--do you have a solution in mind?
Ravi
Spotify taking responsibility and investigating what libcef is dependent on in libgcrypt11 and why it cannot be linked with libgcrypt20? It's very difficult to do this when Spotify is stripping away all the symbols from the shared library libcef.so which is bundled into the release.
Forcing users to install deprecated dependencies outside of repositories is escaping responsiblity. What botheres me even more is the fact that no one from spotify is responding to this thread. And the lack of a ticketing system makes it impossible to get any response. A 'community' isn't a ticket solution!
I agree that I cannot "Accept as Solution" any of these. And neither should they, nor should they encourage by inaction, their listeners and subscribers who pay, to accept a security hole as a solution.
This has clearly been an issue for months. They would never leave the iOS, Android, Windoze users out in the rain like this! If it had been an issue that absolutely stopped users from using the program entirely on any of those platforms they would have fixed it immediately, regardless of any user-base disparity. iOS updates to Spotify come practically twice a month.
Looks like a new testing version does not have this problem:
http://repository-origin.spotify.com/pool/non-free/s/spotify-client/
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
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 🙂
sata, thanks, and oops I didn't realize the updated package exists in the testing repo 🙂
@sata wrote:
[...] Apt repositories exist so you can upgrade your installed software when there is an upgrade path available [...]
Thanks for the tip, this works for me. If you added the repo using the Spotify install guide the file you'll want to edit is /etc/apt/sources.list.d/spotify.list
I guess asking for the i386 version is asking too much 😞
There is version 0.9.4.183.g644e24e.428-1 for i386 in the repository repository.spotify.com
spotify-client_0.9.4.183.g644e24e.428-1_i386.deb
For me the solution found in this blog post did the trick (Ubuntu 15.04) (resolving the libgcrypt11 issue):
"To fix the issue, just download and install the package from the repository of Ubuntu 14.04 LTS.
The solution posted by MarcOS (install the testing version from http://repository-origin.spotify.com/pool/non-free/s/spotify-client/) works for me (although it gives a "experienced an internal error" window, but it doesn't seem to affect functioning)...
Hi,
On a fresh debian jessie install, I experienced the same problem so I changed source to "testing" and upgraded spotify-client package.
However, I was still getting an error about libcurl.so.4 missing, and managed to fix it by installing "libcurl4-openssl-dev" (maybe "libcurl3" alone was enough.)
Still, it would be great to have a fully functionnal package in the stable repository, with all dependicies mentionned.
Regards,
Thanks man! Works for me 😉
A way that might be better (depending on whether you are ready to stay on the testing version of spotify all along or not) is to replace the lines in the code before of MarcosOS:
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
By these one:
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
The version of spotify I ended up with is a little newer:1.0.15.137
The previous solution is most likely not working anymore because the testing version has been updated and thus the 1.0.7.153 has just been removed from the repository.
It will also automatically update spotify when the testing version is updated.
The whole code is thus 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' 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 spotify &
The first two lines might even be useless, but I have not tested.
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…