Linux: Spotify crashes after login

[kolAflash]

Could you please fix this.

https://forum.manjaro.org/t/spotify-crashes-after-login/14246

> it crashes when I try to log me.

Just experienced exactly that same issue, running openSUSE Linux 42.2 and
spotify-client_1.0.45.186.g3b5036d6-95_amd64.deb


This workaround helped:
> Install spotify-legacy (0.9.x) first, log in then install spotify (1.x).

Using: spotify-client-0.9.17_0.9.17.8.gd06432d.31-1_amd64.deb

Using libgcrypt11 from here:
http://download.opensuse.org/repositories/home:/awissu/openSUSE_Leap_42.2/x86_64/libgcrypt11-1.5.4-2...


Should be easily reproduceable with any openSUSE 42.2 system.

It just cost me over 2 hours to figure that out.
Annoying!

[jooon]

Very likely the same crash that is mentioned in this thread.

https://community.spotify.com/t5/Desktop-Linux-Windows-Web-Player/Spotify-1-0-45-186-crashes-on-logi...

[mattelacchiato]

If it's allowed, I could post the 1.0.44.100 deb file. This could help others, because the old version is not available in the repository. May I?

[jooon]

The 1.0.44.100 deb is still available in the stable channel.

http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages

http://repository.spotify.com/pool/non-free/s/spotify-client/

[mattelacchiato]

Ah, thanks! I got the wrong channel (testing)...

[jooon · Accepted solution]

Should be fixed now with 1.0.47 in testing.

[cimenx]

Same here with Ubuntu 16.04

> spotify-client amd64 1:1.0.77.338.g758ebd78-41

Error message in terminal

ATTENTION: default value of option force_s3tc_enable overridden by environment.
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  set_option: Cannot assign requested address
fish: “spotify --showconsole” terminated by signal SIGABRT (Abort)

[Namestaken]

Same error from Spotify 1.0.77.338.g758ebd78-41 installed with Snap on 4-23-2018.

See attached, forum would not let me post the error.

[mirkowart]

same error on ubuntu 16.04 LTS after update application to version 1.0.77.338.g758ebd78-41 

[jooon]

The problem in 1.0.77 is different from the one in 1.0.44 which is what this thread was about.

It has been reported here:

https://community.spotify.com/t5/Desktop-Linux/1-0-77-core-dumps/m-p/4463033/highlight/true#M16352

Possibly fixed in 1.0.79.