protonscr

Pulseaudio crash when starting broadcast

steamopen AudioStreamingDistro Family: Arch
ValveSoftware/steam-for-linux#8844 · opened 2022-10-10 by extract · updated 2023-09-08 · 9 comments · github
Eextract 2022-10-10 github

Your system information

  • Steam client version (build number or date): Oct 7 2022 at 22:29:39
  • Distribution (e.g. Ubuntu): arch linux
  • Opted into Steam client beta?: Yes, tried without as well (Oct 6).
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Hi, I was trying to use steam broadcast to share my game play with my friend.
It worked previously and very well. Today, however, something must've changed.
I tried streaming and once my friend joined pulseaudio crashed. This can be seen in the log below.
I've updated my system after this started and nothing changed. I've restarted plenty of times to no avail. I've managed my pulseaudio devices so there's only 1 output and 1 input and it still fails.

https://gist.github.com/extract/e34242c087ad9ba726cae8e72bea887c
As I'm suspecting currently there is some issue with the sinks when they are being made causing pulseaudio to crash.

Describe what you expected should happen and what did happen.
What should've happen is what happens consistently every other day and is that audio does not crash once broadcast have started. What happened is that pulseaudio crashes. I've tried using pipewire but that one has way more issues than pulseaudio does.

Steps for reproducing this issue:

  1. Start game and broadcast
  2. Friend joins broadcast
  3. Pulseaudio crashes and no sound whatsoever before restarting the applications and (sometimes) reconnecting the audio devices.
Kkisak-valve maintainer 2022-10-10 github

Hello @extract, this probably should also be mentioned to the Pulseaudio dev(s) to ponder on their side as well.

JJarnoKai 2022-10-12 github

This affects me as well. Starting remote play together crashes pulseaudio with the same log messages but randomly it might not.
Ubuntu 22.04, pulseaudio 15.99.1, steam beta oct 7

Ggwemmie 2022-11-07 github

I was streaming a lot just fine 2 hours ago, had never seen this bug. Now it's happening every time.

Arch Linux, pulseaudio 16.1, regular up-to-date client

ZZer0XoL 2022-11-19 github

Please fix this

Ggwemmie 2022-11-19 github

I have a hunch--the step to reproduce could be when you have a module-null-sink running. It hasn't happened to me at all since my last comment, and when it was happening back then, I was running the RNNoise noise suppression module per their non-Pipewire instructions (which involve creating a null sink). And I vaguely remember Steam having an issue when a null sink was running in the distant past.

JJarnoKai 2022-12-09 github

I recently started using PipeWire as per this guide: https://ubuntuhandbook.org/index.php/2022/04/pipewire-replace-pulseaudio-ubuntu-2204/
And have had remote play together work flawlessly at least once. I will come back to report if the issues come back.

Uulibte 2023-01-18 github

JarnoKai i tried the same thing as you and it worked for me too, thanks a lot.

Mmatthijskooijman 2023-03-10 github

I had a similar problem a few months ago with Remote Play Together and Spiritfarer where the log (IIRC journalctl) showed an assertion failure related to module-combine-sink. I then solved this by simply removing /usr/lib/pulse-15.99.1+dfsg1/modules/module-combine-sink.so. I'm not sure if it is the same problem described in this issue (maybe just something with similar symptoms), but wanted to mention this. I also had module-null-sink loaded.

Right now, I'm having issues again, but without any error messages or pulseaudio crashes. It also happens with pipewire (which seems to be the default now in Ubuntu 22.10). I suspect that his is a completely different issue, though it is audio related (since things do work if I disable both pulseaudio and pipewire-pulse, then I can run the game but without audio).

KKiiriot 2023-09-08 github

Replying to https://github.com/ValveSoftware/steam-for-linux/issues/8844#issuecomment-1464547387

I fixed it by doing as matthijskooijman said, if anyone is still having this issue! (Ubuntu 22.04)