Ubuntu 19.04 deb package segfault

Reply

Ubuntu 19.04 deb package segfault

yuusou
Regular

 

Plan Premium

Country US

Device Laptop

Operating System Ubuntu 19.04

 

My Question or Issue

Spotify is crashing with the latest update (1.1.5); rolling back to 1.0.98 solved the issue.

The issue seems to be with curl and gnutls, though I don't want to post logs because they're quite revealing I believe.

86 Replies

anselan
Casual Listener

As of today (?) Spotify seems to be working just fine on my Pop!_OS (Ubuntu 19.04). And I did not make any changes.

pejaham
Newbie

Doing this before every start of Spotify helps. What a pain.

 

rm -r $HOME/.cache/spotify

Panteroide
Regular

@0x783czar thanks! I think you've compiled all the best-practices available on your post! 🙂

hvontres
Newbie

Thank you, that seems to work for me as well 🙂

chris208
Casual Listener

@meijero wrote:

If you want to upgrade to the latest version now, downloading and installing these packages is probably the only solution. Install gnutls30 first

 

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

 

You shouldn't have any issues by upgrading these packages, but:

Rolling back to the original packages, in case of problems or broken depenScreenshot Synaptic.pngdencies, is very easy if you follow these steps.

 

1 Install Synaptic (package manager) if required

2 Find the first package you wish to downgrade and select it.

3 In the Synaptic toolbar under "Package" select "Force version", then select the desired version you want to downgrade to.

4 Click the button "Force version"

5 Repeat the process for the second package.

6 Press the "apply button" in the Synaptic toolbar to execute the downgrade.

 

Note: downgrade both packages simultaneously, as I am describing, otherwise you might have fo fix broken dependencies.

Best regards, and have fun with trying out these solutions.

 

Otto


Cool that you figured this out, I hope the developers are reading this thread so they can fix it.

However I don't think users shoul forcefully mess up their libraries and cause dependency issues down the line.

 

I think the developers at Spotify shouldn't develop on OS's that are not current, neither out-of-date nor nightlies with newer libs. My system is a normal up-to-date Ubuntu 19.04, I have libgnutls30 3.6.5-2 and libcurl3-gnutls 7.64.0-2. There are no upgrades available at this time. I would hope Spotify has some kind of CI pipeline that tests basic features like starting up at all on current systems, but this issue doesn't really seem to indicate they do, or perhaps they didn't make one for 19.04 yet?

-olo-
Visitor

Worked for me using the versions:

 

dpkg --list | grep gnutls

ii libcurl3-gnutls:amd64 7.64.0-4 ...
ii libgnutls30:amd64 3.6.7-4 ...
ii libgnutls30:i386 3.6.7-4 ...

 

cat /etc/lsb-release

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.04
DISTRIB_CODENAME=disco
DISTRIB_DESCRIPTION="Ubuntu 19.04"

... with Mint desktop

chris208
Casual Listener

What you could also do, if you are desperate to get this working is this:

Download the two files that Otto referred to, but from another source, one that we can verify:

wget http://ftp.nl.debian.org/debian/pool/main/c/curl/libcurl3-gnutls_7.64.0-3_amd64.deb
wget http://ftp.nl.debian.org/debian/pool/main/g/gnutls28/libgnutls30_3.6.8-1_amd64.deb
sha256sum libcurl3-gnutls_7.64.0-3_amd64.deb | grep b9f78db7f991564da9e972f1c9ac197bd73b836bbc6901fde12df97639538f15 && echo "File checksum OK" || echo "File checkusm is BAD\!"
sha256sum libgnutls30_3.6.8-1_amd64.deb | grep e49e9c1c82755f8ff11f5b3846bd4a4b4c8c62953a38612485ca2437b6a6c41c && echo "File checksum OK" || echo "File checkusm is BAD\!"

 

You should see "File checksum OK" twice here, if you see "File checkusm is BAD!" even once, check the URL's again, don't install if you keep getting this output.

 

mkdir ~/.config/spotify/temp-fix-broken-libs/
dpkg-deb -x libcurl3-gnutls_7.64.0-3_amd64.deb  ~/.config/spotify/temp-fix-broken-libs/
dpkg-deb -x libcurl3-gnutls_7.64.0-3_amd64.deb  ~/.config/spotify/temp-fix-broken-libs/
dpkg-deb -x libgnutls30_3.6.8-1_amd64.deb  ~/.config/spotify/temp-fix-broken-libs/

That places the libraries that are required to make Spotify run again in a temporary location. To start Spotify using them you need to run:

 

LD_LIBRARY_PATH=~/.config/spotify/temp-fix-broken-libs/usr/lib/x86_64-linux-gnu /usr/bin/spotify
You could make a shortcut for that like this: 
 
sudo tee /usr/bin/spotify-temp-fix <<EOF

#!/bin/bash
LD_LIBRARY_PATH=~/.config/spotify/temp-fix-broken-libs/usr/lib/x86_64-linux-gnu /usr/bin/spotify
EOF

sudo chmod +x /usr/bin/spotify-temp-fix
Now run spotify-temp-fix to start spotify.
 

yuusou
Regular

The only solutions I'd personally recommend other than rolling back is @chris208's solution or snap/flatpak.

 

The thing with non-deb solutions such as snap and flatpak is that it's always slower and sometimes a bit buggy.

I'd definitely avoid installing the debian-repo packages, that can really break your system.

 

All the other "solutions" are temporary fixes that will conk out eventually as the issue clearly lies with gnutls.

I say "solutions" because the only real solutions is either an update to spotify or an update to gnutls from Ubuntu/Canonical.

dinandmentink
Casual Listener

Anyone from spotify reading this?

Juanttc
Casual Listener

I've tweeted about this problem, but the first answer is absolutely not satisfying 😞

 

https://twitter.com/NicolasRouanet/status/1139463336163192832

chris208
Casual Listener

@Juanttc wrote:

I've tweeted about this problem, but the first answer is absolutely not satisfying 😞

 

https://twitter.com/NicolasRouanet/status/1139463336163192832


That's unfortunate, I can only speak for myself.. my premium subscription will be canceled without a working Linux client.

thereal_rjf
Gig Goer

having similar problems (seg faults) on deb buster. happens randomly on startup, seems to happen less often when process slowed down running under ltrace so maybe some kind of race condition... see 

 

https://community.spotify.com/t5/Desktop-Linux/Segmentation-fault-core-dumped-is-back/td-p/4771027

 

looks like a problem with pointers to buffers or something. 

dlu
Gig Goer

This is not the fault of the spotify-client. It is due to [1] and [2] in curl. Debian buster and Ubuntu eoan have the patched package already, while disco is unpatched. Someone would need to write a bug report so that the patch is included in the current disco-updates.

Update: I found the debian bug report under which the patches came into buster [3].

Update2: And there is the Ubuntu bug report [4].

 

[1] https://github.com/curl/curl/issues/3541

[2] https://github.com/curl/curl/issues/3542

[3] https://bugs.debian.org#927471

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

dinandmentink
Casual Listener

Went to the Twitter as well. Got a positive response there:

 

https://twitter.com/SpotifyCares/status/1139896730852515840 . Looking forward to an update.

the_furai
Casual Listener

If that fixes it, maybe it's worth to wrap it in a script that loads these libraries from some custom and not system-wide install location. Could that be feasible?

carlihland
Casual Listener
Out of scope. This ticket refers the Deb package.

But can confirm that the snap works.

FabiG15
Casual Listener

I have the same problem on both my devices:

 

Notebook with Ubuntu 19.04 (KDE)

and PC with Ubuntu 19.04 (Gnome)

 

Thread 26 "Curl Thread" received signal SIGSEGV, Segmentation fault.

 

carlihland
Casual Listener

Confirmed, Ubuntu 19.04

dinandmentink
Casual Listener

Can confirm on Spotify version 1.1.5.153 and ubuntu 19.04. Client won't start on multiple machines.

benvantende
Newbie

Confirmed here as well.

mrvanes
Regular

Thought nudging the Ubuntu community could be helpful as well:

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

SUGGESTED POSTS