Segmentation fault (core dumped) is back

[hypergig]

Plan

Premium

Country
US

Operating System

Ubuntu 19.04

My Question or Issue

Today I received a new update to the spotify linux client

spotify-client:amd64 (1:1.1.0.237.g378f6f25-11, 1:1.1.5.153.gf614956d-16)

After which, spotify would crash immediately after starting up. Starting the client from a terminal yielded the following error

Segmentation fault (core dumped)

After troubleshotting for a while, I noticed the problem stopped happening when I deleted my local config directory

rm -rf ~/.config/spotify

Clearly this isn't a solution so I dug in a little, spelunking through the output from running 

spotify --show-console

One line stood out from the rest

13:00:33.032 W [collection_local_bans_file.cpp:51] bans: could not read local bans file: /home/<me>/.config/spotify/Users/<my account>-user/local_bans.pb

(obvious private stuff redacted)

So I checked and I don't have that file. But I do have this file

/home/<me>/.config/spotify/Users/<my account>-user/local-files.bnk 

So I tried deleting it to see what happened and started the spotify client back up and it worked but only from the terminal.  However, after a few more tries, it only worked part of the time 😕 So I am not sure what to make of that anymore. 

I would be happy to send my logs to someone in engineering if you would like.

EDIT

It is totally sporadic. Without fiddling with anything and starting the client works about 1 out of 3 times. 

[hypergig]

so this was the first thing I tried and when i compared versions they were exactly the same, so it was no surprise they both suffered the same issue when the snap version sig faulted on me 😕

honestly, it can be nothing else but a race condition... if you slow your machine down or artificially slow down the app with something like cpulimit, the app usually starts up.. it is completely unusable but it didn't seem to sig fault as often.. the fact that we can't consistently repro it within it self points to a race condition.

there is not much we can do but wait for them to patch it in engineering, or wait for them to open high q in the webclient, i already looked for the old version of the app but they seem to have pulled it 

[kfunk]

For the record, for all Ubuntu users, this is the downstream bug report: 

https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882

[treepleks]

An excellent workaround that worked fine for me on Ubutu 19.04 was to
install more recent versions of libgnutls and rcu-gnutls from debian.

Just installed

http://ftp.us.debian.org/debian/pool/main/g/gnutls28/libgnutls30_3.6.8-1_amd64.deb

http://http.us.debian.org/debian/pool/main/c/curl/libcurl3-gnutls_7.64.0-3_amd64.deb

and spotify runs fine. The problem seems to come from gnutls+multithreading.

[thereal_rjf]

did you read the rest of the thread ? 😉

[rushlife]

the same by me, i cannot run spotify at least 2 weeks...

any advice ?

(SIGSEGV) (core dumped.......

[banele]

Yes! treepleks 's tip was definetely on the right track.

Managed my way out of the segmentation faults on Ubuntu 19.04 (disco) x64 by installing the latest eoan libs.
Just go to https://packages.ubuntu.com/eoan/***** to download the following libs (only amd64 version for most, but both amd64 and i386 for libgnutls30 and libtasn1-6):
libcurl3-gnutls, libgnutls28-dev, libgnutls30 (amd64 and i386), libgnutls-dane0, libgnutls-openssl27, libgnutlsxx28, libtasn1-6 (amd64 and i386), libtasn1-6-dev
Just 'sudo dpkg -i lib*' on the folder you've downloaded those and spotify should load without any SegFaults!

[edathi]

Here's some commands you can run real quick to fix it (taken from 0x783czar on another thread, but this is the first result on google so I figure I'll add it here to help save people some time):

"

Also running Pop_OS! here (19.04). Using some of the earlier posts I got it working after doing the following. If the last command doesn't work, run 'apt --fix-broken install' and try the last command again. After doing this it started working for me!

sudo apt install libssh2-1

curl http://ftp.us.debian.org/debian/pool/main/g/gnutls28/libgnutls30_3.6.8-2_amd64.deb -o ~/Downloads/libgnutls30_3.6.8-2_amd64.deb 

curl http://ftp.us.debian.org/debian/pool/main/g/gnutls28/libgnutls30_3.6.8-2_i386.deb -o ~/Downloads/libgnutls30_3.6.8-2_i386.deb 

curl http://http.us.debian.org/debian/pool/main/c/curl/libcurl3-gnutls_7.64.0-4_amd64.deb -o ~/Downloads/libcurl3-gnutls_7.64.0-4_amd64.deb

sudo dpkg -i ~/Downloads/libcurl3-gnutls_7.64.0-4_amd64.deb ~/Downloads/libgnutls30_3.6.8-2_amd64.deb ~/Downloads/libgnutls30_3.6.8-2_i386.deb

The reason for this is, as far as I understand it, is that there is a missing patch in the libcurl3-gnutls package in Ubuntu based distributions. However Debian has patched their version of the package. And so installing their version of the package (and its needed dependencies) will get it working."

[edathi]

Also running Pop_OS! here (19.04). Using some of the earlier posts I got it working after doing the following. If the last command doesn't work, run 'apt --fix-broken install' and try the last command again. After doing this it started working for me!

sudo apt install libssh2-1

curl http://ftp.us.debian.org/debian/pool/main/g/gnutls28/libgnutls30_3.6.8-2_amd64.deb -o ~/Downloads/libgnutls30_3.6.8-2_amd64.deb 

curl http://ftp.us.debian.org/debian/pool/main/g/gnutls28/libgnutls30_3.6.8-2_i386.deb -o ~/Downloads/libgnutls30_3.6.8-2_i386.deb 

curl http://http.us.debian.org/debian/pool/main/c/curl/libcurl3-gnutls_7.64.0-4_amd64.deb -o ~/Downloads/libcurl3-gnutls_7.64.0-4_amd64.deb

sudo dpkg -i ~/Downloads/libcurl3-gnutls_7.64.0-4_amd64.deb ~/Downloads/libgnutls30_3.6.8-2_amd64.deb ~/Downloads/libgnutls30_3.6.8-2_i386.deb

The reason for this is, as far as I understand it, is that there is a missing patch in the libcurl3-gnutls package in Ubuntu based distributions. However Debian has patched their version of the package. And so installing their version of the package (and its needed dependencies) will get it working."

[grimpressive · Accepted solution]

You are the man.

Can confirm that standard Spotify (.deb not snap) now works and starts as intended.

No need to install i386 packages actually.

And the versions from the previous post fails (fix broken install WON'T work) because they are just broken links to the FTP; these are the correct versions that allow apt to continue working properly.

curl http://http.us.debian.org/debian/pool/main/libt/libtasn1-6/libtasn1-6_4.14-2_amd64.deb -o ~/Downloads/libtasn1-6_4.14-2_amd64.deb

curl http://http.us.debian.org/debian/pool/main/c/curl/libcurl3-gnutls_7.64.0-4_amd64.deb -o ~/Downloads/libcurl3-gnutls_7.64.0-4_amd64.deb

curl http://ftp.us.debian.org/debian/pool/main/g/gnutls28/libgnutls30_3.6.9-4_amd64.deb -o ~/Downloads/libgnutls30_3.6.9-4_amd64.deb

[DaveNZ1]

Thanks grimpressive, Awesome - works!

When downloaded click on each package and install. Reboot.

[pega041]

That didn't work for me, but it did send me in the right direction.

Apparently those libraries are being upgraded constantly, so two of them are currently giving 404. My bet was to get the immediate following version.

This is wat I did (as root):

cd /tmp
wget http://http.us.debian.org/debian/pool/main/libt/libtasn1-6/libtasn1-6_4.14-3_amd64.deb
wget http://ftp.us.debian.org/debian/pool/main/g/gnutls28/libgnutls30_3.6.9-5_amd64.deb
wget http://http.us.debian.org/debian/pool/main/c/curl/libcurl3-gnutls_7.64.0-4_amd64.deb
dpkg -i libtasn1-6_4.14-3_amd64.deb
dpkg -i libgnutls30_3.6.9-5_amd64.deb
dpkg -i libcurl3-gnutls_7.64.0-4_amd64.deb

It should work right out of the box, but just in case it might be useful to run aptitude install -f.

(If you don't know what you're doing, don't do that!).

Cheers!

PS: If this happens again to anyone, just follow the links, remove the filename from the URL and look in the list a file with the same name but with newer versions (i.e. bigger numbers in the last part). Don't try to jump to the last available version, just go to the immediate newer version.

[arran4]

I was able to trigger this to start happening when I went to a location which had a Wifi Login capture portal. I suspect it's creating these files directly from a download without verifying

[shegeley]

Yesterday I had the same problem. Spotify and chromium browser were installed with snap. After I deleted them as snaps and installed via package manager the problem was gone. I don't know what the source. The last-big-thing that happen on my laptop is: new nvidia-drivers came out and installed automatically.

[EoGn]

For everyone where it not woked at this time (08.09.2023)
Here is my solution:
Just "sudo apt remove spotify-client" and do: "sudo rm -rf ~/.config/spotify/"

and reinstall it with:

curl -sS https://download.spotify.com/debian/pubkey_7A3A762FAFD4A51F.gpg | sudo apt-key add -
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

That worked for me