The return of the libssl trouble on Linux

[topyli]

Running Debian testing/sid (stretch), spotify-client from Spotify's testing repository no longer works.

spotify: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

Looks like a recurring theme, as we have just recently survived the libssl0.9.8 to 1.0.0 transition, but we're going to have to enjoy 1.0.2. I doubt Debian will be easily persuated to stop upgrading their security related libraries so that we can run our favorite non-free software. Someone else will have to be flexible here 🙂

[DanielJCosta]

Even with ln -s from the new library this problem persists.

Any news about this??? 

[jenwe]

Same Problem here, clean install of Debian testing.

Just download & install the 1.0.0 version (https://packages.debian.org/jessie/libssl1.0.0) and it should work.

[AzP]

This is what I'm seeing on Gentoo... It would be nice if Spotify updated their libraries to something fairly modern, just to keep in sync with Linux distributions.

peter@skare ~ $ spotify
/opt/spotify/spotify-client/spotify: /usr/lib64/libssl.so.1.0.0: no version information available (required by /opt/spotify/spotify-client/spotify)
/opt/spotify/spotify-client/spotify: /usr/lib64/libcrypto.so.1.0.0: no version information available (required by /opt/spotify/spotify-client/spotify)
/opt/spotify/spotify-client/spotify: /usr/lib64/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /opt/spotify/spotify-client/spotify)

This is my Spotify package information:

[I] media-sound/spotify
     Available versions:  1.0.27^ms {gnome pax_kernel pulseaudio}
     Installed versions:  1.0.27^ms(14:27:35 2016-04-23)(gnome pulseaudio -pax_kernel)
     Homepage:            https://www.spotify.com/ch-de/download/previews/
     Description:         Spotify is a social music platform

[Gryzly]

It's working. Thanks a lot.

[matino]

> Just download & install the 1.0.0 version (https://packages.debian.org/jessie/libssl1.0.0) and it should work.

This may work but it's not a recommended way, since you're downgrading to a version with security issues.

I'd rather expect a fix from the spotify team instead.

[camgaertner]

agreed, don't really want to subject my machine to known exploits just to use spotify...

[QuartzStar]

I am using Kali and it works for me.

download:

http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.0.0_1.0.2g-1ubuntu4.1_amd64.deb

run this on your terminal:

dpkg -i libssl1.0.0_1.0.2g-1ubuntu4.1_amd64.deb

[bulaka]

As OpenSSL is not backwards compatible, I see that this problem will reoccur everytime there is a jump in the version... Had to downgrade to libssl1.0.0 in Debian to keep my spotify-client working. Not optimal.

[topyli]

Spotify probably is not interested in supporting Debian testing/Sid, or development versions of any other distribution, and I don't expect them to. Still, I wonder why Spotify always seems to "just work" on Arch Linux, which certainly keeps up with the latest versions of openssl and other libraries. For reference, here's the Spotify PKGBUILD in the AUR, and from what I see the maintainer changes nothing in the Debian package.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=spotify

[anarcheano]

For those who reeaaallly don't want to blow up the system ssl library, what I did was:

- Download OpenSSL 1.0.0 source (ftp://ftp.openssl.org/source/, 1.0.0 latest patch is 1.0.0t)

- sudo aptitude install zlib1g-dev libssl-dev

  - (You may also need build tools, like, make and gcc, I already have those installed here)

- Extract and get into openssl source directory

$ ./config --prefix=/opt/openssl1.0.0 threads shared

$ make

# make install

Now create a script and make it executable:

# $EDITOR /usr/local/bin/spotify-opt

------ Insert Content:

#!/bin/sh

export LD_LIBRARY_PATH=/opt/openssl1.0.0/lib

/usr/bin/spotify

------- END

# chmod +x /usr/local/bin/spotify-opt

And create a desktop entry (I copied the one that comes with spotify on /usr/share/applications, and modified it):

# $EDITOR /usr/local/share/applications/spotify-opt.desktop

----- Content

[Desktop Entry]
Name=Spotify - /opt SSL
GenericName=Music Player
Comment=Spotify streaming music client
Icon=spotify-client
Exec=/usr/local/bin/spotify-opt %U
TryExec=spotify-opt
Terminal=false
Type=Application
Categories=Audio;Music;Player;AudioVideo;
MimeType=x-scheme-handler/spotify;

---- END

Notice that I modified three options from the original:

The Name, so I can differentiate my desktop entry from the original,

Exec and TryExec, so this entry run /usr/local/bin/spotify-opt instead of /usr/bin/spotify.

I believe most people will find this complicated and not worth it, but if you are one that don't like messing up with your security libraries, that's a better fix than the Jessie package.

Hope it helps.

[anarcheano]

Oh... This was really stupid... There is an way more awesome/simple solution: Use flatpak.

http://flatpak.org/

flatpak and flatpak-builder are already available on debian stretch repos.

https://github.com/alexlarsson/spotify-app

Just Works ™

[jooon]

---

@anarcheano wrote:

Oh... This was really stupid... There is an way more awesome/simple solution: Use flatpak.

http://flatpak.org/

flatpak and flatpak-builder are already available on debian stretch repos.

https://github.com/alexlarsson/spotify-app

Just Works ™

---

Looks nice. We should totally make an official flatpak distribution of Spotify for Linux.

[JohanCR]

It works man, I appreciate it. I am also using Kali Linux.

[mdriftmeyer]

Not very useful when flatpak just dumps to terminal and not what it is supposed to do: download the Sdk and archive in the .local repository.

Debian Sid: Flatpak 0.6.8.

This is dumping to terminal has been a common problem with the flatpak.org site.

[serv03]

This worked perfectly for me. Thank you so much!

[topyli]

BTW, Debian Stretch is now stable, and the Spotify package still refuses to install.

[somnophobe]

using Debian Buster, I was able to install spotify by first installing dirmngr (needed for the key registration command on spotify's instructions page) and then adding Jessie-Backports:

deb http://ftp.debian.org/debian jessie-backports main

as an apt source (it's the last version supporting 1.0.0, but looks like it's actually a port of 1.0.2 providing 1.0.0 compatibility)

for other systems:

• the Arch Spotify AUR is modified to depend on `openssl-1.0` as opposed to a specific patch version, so that should work if you're AUR-based
• Ubuntu just calls all 1.0.x 1.0.0, which is probably the root of the problem. edit: root problem confirmed
• this thread has flatpaks, if you're into that

more details on the issue:

• noted as an issue with the Spotify Play Button (website thing) May 2016
• acknowledged and on Spotify's internal bugtracker October 2016
• this thread we're in now is the oldest reference to this issue I've found (February 2016)

[whati001]

Hi all,

I run into the same issue with debian stretch.

But found an repository for libssl1.0.0 on the package.debian.org webpage.

https://packages.debian.org/jessie/amd64/libssl1.0.0/download

Added to /etc/apt/sources.list or sources.list.d/... as you like.

apt-get update

apt-get install libssl1.0.0 

DONE.

Rerun the apt-get install spotify-client and everything went smooth.

[jooon · Accepted solution]

After almost two years, this has finally been "fixed".

Spotify 1.0.69 in the testing repository now (soon stable) can dynamically load different version of libcrypto.so (from the libssl* packages).