Segmentation fault (core dumped) is back

Solved!
Reply

Segmentation fault (core dumped) is back

hypergig
Regular

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. 

1 ACCEPTED SOLUTION
Solution!

grimpressive
Casual Listener

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

View solution in original post

31 Replies

shegeley
Visitor

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.

arran4
Visitor
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

hypergig
Regular

this seems to be a work around

 

$ until spotify; do echo try again; done
[0100/000000.820699:FATAL:memory.cc(22)] Out of memory. size=4194304
Segmentation fault (core dumped)
try again
Segmentation fault (core dumped)
try again
Segmentation fault (core dumped)
try again
[0100/000000.589403:FATAL:memory.cc(22)] Out of memory. size=4194304
Segmentation fault (core dumped)
try again
Segmentation fault (core dumped)
try again

Please turn your head away from your computer before throwing up, I am not responsible for broken keyboards and/or laptops

treepleks
Casual Listener
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.
Solution!

grimpressive
Casual Listener

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

View solution in original post

pega041
Newbie

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.

DaveNZ1
Visitor

Thanks grimpressive, Awesome - works!

When downloaded click on each package and install. Reboot.

banele
Visitor

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
Newbie

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."

thereal_rjf
Gig Goer

did you read the rest of the thread ? 😉

grimpressive
Casual Listener

20 minutes to get it running.

 

Woah.

tomaspinho
Casual Listener

Snap version runs well (compatible libraries are probably inside the snap)

grimpressive
Casual Listener

Totally disagree.

 

Snap version has no media keys working AND suffers from segfault just like the .deb one.

 

...at least, on my machine running an up-to-date 19.04 Ubuntu.

tomaspinho
Casual Listener

Also running up-to-date Ubuntu 19.04. The snap version hasn't crashed once. But it does take longer to spawn.

hypergig
Regular

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
Newbie

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

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

kaloshade
Newbie

Im also getting the crash. I ran the same command and piped the output to a file. Uploading the file here. Would just post it but the message cant exceed 20k chars.

thereal_rjf
Gig Goer

Same thing here. Tried to post a reply about 6 times yesterday but gave up in the end. 

thereal_rjf
Gig Goer

base64 encoded my reply to get past this ridiculous forum filtering 

 

 

U28gbm93IGl0IHNlZW1zIHRvIGJlIGxldHRpbmcgbWUgcmVwbHkgLSBJJ20gcnVubmluZ8KgU3Bv
dGlmeSB2ZXJzaW9uIDEuMS41LjE1My5nZjYxNDk1NmQgb24gRGViaWFuIC4KCgoKSXQncyB0b3Rh
bGx5IHNwb3JhZGljLCB0aGUgcHJvY2VzcyBnZXRzIGtpbGxlZCBieSBTSUdTRUdWIGltbWVkaWF0
ZWx5IGFmdGVyIGEgY2FsbCB0b8KgMzUuMTg2LjIyNC41MyB3aGVuIGl0IGRpZXMuIEl0IHNlZW1z
IHRvIGdvIGZyb20gd29ya2luZyB0byBkaWVpbmcgc3BvcmFkaWNhbGx5LCBpbiBhbGwgY2FzZXMg
SSBjYW4gc2VlIGZyb20gdGhlIGxvZ3MgaXQgY29ubmVjdHMgZm9uZSwgcHVsbHMgZGVsdGFzIGZy
b20gcGxheWxpc3RzIGV0YyB0aGVuIGdldHMgdG/CoFtnYWlhX2xvZ2luX3N0YXRlX29ic2VydmVy
LmNwcDo0Ml0gcmVjZWl2ZWQgbmV3X2Nvbm5lY3Rpb25faWQgdGhlbgoKCgowOToxMzowOS42ODEg
RCBbZ2FpYV9tYW5hZ2VyLmNwcDo0MDkgICAgICAgICAgICBdIEdBSUE6IEdhaWFNYW5hZ2VyOjpz
dGF0ZVRyYW5zaXRpb24sIGtTZXJ2aWNlU3RhdHVzU3RvcHBlZC0+a1NlcnZpY2VTdGF0dXNSdW5u
aW5nCjA5OjEzOjA5LjY4MiBEIFtnYWlhX21hbmFnZXIuY3BwOjExNDYgICAgICAgICAgIF0gR0FJ
QTogVElNSU5HKDIwNzUwNDkxNjUpIEdhaWFNYW5hZ2VyOjpzZW5kSGVsbG9IZWxwZXIKMDk6MTM6
MDkuNjk5IEQgW2dhaWFfbWFuYWdlci5jcHA6MTE0NiAgICAgICAgICAgXSBHQUlBOiBUSU1JTkco
MjA3NTA0OTE4MikgR2FpYU1hbmFnZXI6OnNlbmRIZWxsb0hlbHBlcgowOToxMzowOS43MjEgSSBb
cmVxdWVzdF9hY2NvdW50aW5nLmNwcDo0MTYgICAgICBdIEhpZ2ggcmVxdWVzdCBsYXRlbmN5OiBo
dHRwczovL3NwY2xpZW50LndnLnNwb3RpZnkuY29tL21ldGFkYXRhIHRvb2sgMTc1IG1zCjA5OjEz
OjA5Ljc3NyBJIFtyZXF1ZXN0X2FjY291bnRpbmcuY3BwOjQxNiAgICAgIF0gSGlnaCByZXF1ZXN0
IGxhdGVuY3k6IGh0dHBzOi8vc3BjbGllbnQud2cuc3BvdGlmeS5jb20vYWRzIHRvb2sgMzc3IG1z
CjA5OjEzOjA5Ljc3NyBJIFtyZXF1ZXN0X2FjY291bnRpbmcuY3BwOjQxNiAgICAgIF0gSGlnaCBy
ZXF1ZXN0IGxhdGVuY3k6IGh0dHBzOi8vc3BjbGllbnQud2cuc3BvdGlmeS5jb20vYWRzIHRvb2sg
Mzc3IG1zCjA5OjEzOjA5Ljc3OSBJIFtyZXF1ZXN0X2FjY291bnRpbmcuY3BwOjQxNiAgICAgIF0g
SGlnaCByZXF1ZXN0IGxhdGVuY3k6IGh0dHBzOi8vc3BjbGllbnQud2cuc3BvdGlmeS5jb20vYWRz
IHRvb2sgMzc5IG1zClNlZ21lbnRhdGlvbiBmYXVsdApOb3Qgc3VyZSBpZiB0aGlzIGlzbid0IGEg
cmFjZSBjb25kaXRpb24gc29tZXdoZXJlIGFyb3VuZCBjb25uZWN0aW9uLiBJdCdzIHRvbyByYW5k
b20gdG8gYmUgc29tZXRoaW5nIG9uIHRoZSBtYWNoaW5lIGFuZCBpdCBjb25uZWN0cyBhbmQgcHVs
bHMgdGhlIHBsYXlsaXN0IGRlbHRhcyBldGMgd2l0aG91dCBmYWlsIGV2ZXJ5IHRpbWUgaXQgc3Rh
cnRzIHJlZ2FybGVzcyBvZiB3aGV0aGVyIGl0IHNlZ2ZhdWx0cyBvciBub3QuwqAK

hypergig
Regular

I may never stop laughing...

 


@thereal_rjf wrote:

base64 encoded my reply to get past this ridiculous forum filtering 

 

SUGGESTED POSTS