sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 0DF731E45CE24F27EEEB1450EFDC8610341D9410
echo deb http://repository.spotify.com stable non-free | sudo tee /etc/apt/sources.list.d/spotify.list
sudo apt-get update
sudo apt-get install spotify-client
spotify
Gtk-Message: 15:55:24.185: Failed to load module "overlay-scrollbar"
[0419/155524.255252:ERROR:nss_util.cc(724)] After loading Root Certs, loaded==false: NSS error code: -8018
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
Aborted (core dumped)
Solved! Go to Solution.
I have created a basic workaround for this issue which involves wrapping the failing system call and ignoring the results of the call to make spotify happy:
Installation instructions are at the top of the GIST
https://gist.github.com/mdierolf/7751f9c4535a6d402438e219617cf4c3
I can confirm that the bug is fixed in Spotify 1.0.79 distributed in Debian testing running on Ubuntu 18.04.
I hope to see Spotify 1.0.79 in Debian stable soon.
I get the same error message after I updated the spotify app via apt. I'm using Ubuntu 17.10 and
Spotify version 1.0.77.338.g758ebd78, Copyright (c) 2018, Spotify Ltd
I get similar error on Ubuntu 16.04
spotify
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
Some NixOS users discovered the same issues and found out that spotify does not crash when you start it without a network connection or with two network connections: https://github.com/NixOS/nixpkgs/issues/39208
But if you have exactly one network connection spotify crashes with this
set_option: Cannot assign requested address
message.
This issue is probably a duplicate of https://community.spotify.com/t5/Desktop-Linux/1-0-77-core-dumps/m-p/4451694.
I have created a basic workaround for this issue which involves wrapping the failing system call and ignoring the results of the call to make spotify happy:
Installation instructions are at the top of the GIST
https://gist.github.com/mdierolf/7751f9c4535a6d402438e219617cf4c3
You saved my day! Your workaround works perfectly. Thanks a lot!
Same problem as:
https://community.spotify.com/t5/Desktop-Linux/1-0-77-core-dumps/m-p/4463033/highlight/true#M16352
Possibly fixed in 1.0.79.
I can confirm that the bug is fixed in Spotify 1.0.79 distributed in Debian testing running on Ubuntu 18.04.
I hope to see Spotify 1.0.79 in Debian stable soon.
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game…