Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Spotify opens too many connections to PulseAudio (Linux)

Solved!

Spotify opens too many connections to PulseAudio (Linux)

After some time Spotify for Linux starts to use too many connections to PulseAudio. This makes it impossible to use any sound on the computer.

 

This shows an output after one day of usage:

http://pastebin.com/E5AVQd62

 

Spotify version 1.0.36.120.g536a862f, Copyright (c) 2016, Spotify Ltd

OS: Debian 8.5 (Jessie)

 

Reply
28 Replies

i have seen this happening regardless of mobile phone use, and starting Spotify with --no-zygote. the phone can be off for hours, as has mine, so Spotify is not being used/opened there. and from time to time, when checking audio mixer, additional Spotify processes will exist.

 

(edit: this is still an issue, after updating to 1:1.2.8.923.g4f94bf0d)

this is still an issue on version 1:1.2.11.916.geb595a67.

hey this should be fixed in 1.2.45.454

I'm not convinced that it's fixed in 1.2.45.454.

miiichael_au_0-1729077067638.png

 

oh no 😞 thanks for testing

hey any chance you could try with 1.2.50.335.g5e2860a8? it should have improved now.

 

Yes, there's a chance. But first:

- it needs to appear in your repo

miiichael_au_0-1732538864203.png

- repository.spotify.com has got to stop dropping the connection partway into the download (apt-cacher-ng does not resume partial downloads)

According Debian there is possibility to restrict spawning of PulseAudio but not sure if this help...Today is PipeWire a reality also in Debian...

Restricting the spawning of pulseaudio basically turns if off altogether, so no, not helpful. 😛

 

I'm sure we'll see Pipewire support in Spotify in *looks at wristwatch* ten years or so (judging from rate of progress at fixing this bug). 😛

Suggested posts