Ubuntu 19.04 deb package segfault

[yuusou]

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.

[anselan]

And.... now it's working again. Huh.

[OMGBosnia]

---

@anselan wrote:

And.... now it's working again. Huh.

---

Is it working after closing and reopening a few times?

[dinandmentink]

Anyone from spotify reading this?

[anselan]

Oh. Seems like it sometimes starts only on the second (or third?) attempt. And sometimes first time.

Wut.

[Juanttc]

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

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

[benvantende]

Confirmed here as well.

[mrvanes]

Thought nudging the Ubuntu community could be helpful as well:

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

[dinandmentink]

Smart thinking. Confirmed.

[the_furai]

Nice, how fast confrimed bugs on ubuntu get resolved?

[user-removed]

---

@the_furai wrote:

Nice, how fast confrimed bugs on ubuntu get resolved?

---

That can take some days to several months depending of the bug's priority and its severity.

[dinandmentink]

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

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

[chris208]

---

@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]

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]

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

[carestad]

For some reason, Spotify works right after I re-connect my wifi or cabled connection. It segfaults and crashes before, but right after re-connecting it works. Weird.

I have also tried downloading the curl related libraries form Debian's package repos here, and that worked, but I did see some version conflicts and had a bit of a APT mess to clean up afterwords, so I am not sure if I would recommend installing the .deb files that has been linked previously.

[dlu]

---

@carestad wrote:

I have also tried downloading the curl related libraries form Debian's package repos here, and that worked, but I did see some version conflicts and had a bit of a APT mess to clean up afterwords, so I am not sure if I would recommend installing the .deb files that has been linked previously.

---

It is not necessary to download and install deb files manually. One can include the eoan apt repository and work with pinning such that libcurl3-gnutls (and dependencies) will be upgraded via the usual apt upgrade leaving other packages untouched.

[thereal_rjf]

This actually makes sense. I think from what I've found in the other forum thread - with the random segfault - I ran the spotify through gdb withthe core dump, found what seems to be the problem with the call to curl, examined the memory contents of the buffer passed to  libcurl-gnutls.so.4->curl_mvsnprintf for its output

29666 1561378833.635000 libcurl-gnutls.so.4->curl_mvsnprintf(0x7f07eaffa8e0, 2049, 0x7f083f6e7588, 0x7f07eaffa8c8)
                                    = 53 <0.002275>

and it contained :

(gdb) x/1s 0x7f07eaffa8e0
0x7f07eaffa8e0: "17 bytes stray data read before trying h2 connection\n"

which I think is because the client is not playing well with threads and is there are h2 connections with things left in them which are not being handled... possibly. Limited to how much poking I can do as it's not open source etc but there you go.

[thereal_rjf]

Sorry I meant to say I am not surprised that restarting the network and loading spotify fixes it until next time for you... due to the above. possibly 🙂 

[thereal_rjf]

I compiled gnutls and curl (compiled against gnutls) from latest source and ran my version of spotify. All fixed. Looks like problem in curl handling of multi events... which rather embarasingly is the problem pointed out by the chap above about the lib curl problems 🙂 Sorry chaps for wasting more of your time. Apollogies for blaming the spotify app here. Cheers.

[vaughan]

The following brought it back for me:

1. snap remove spotify  (or apt-get purge spotify-client if using the deb package)

2. I used "locate spotify" to remove every mention of spotify from my system (well, except some icons, which I didn't think would matter).

3. snap install spotify

4. spotify  (I got to the login window, clicked "login with facebook", nothing seemed to happen, so I killed spotify).

5 spotify   (worked the second time)