Hello,

After todays update, I no longer have any output audio sound detected. I have a soundblaster audigy 2zs

The weird thing is that during boot and shutdown I head my speakers "come on" (a sound like a "pop" when the o.s. initializes the sondcard/speakers) like it always did.

when typing cat /proc/asound/cards I get

0 [Audigy2 ]: Audigy2 - SB Audigy 2 ZS [SB0350]
SB Audigy 2 ZS [SB0350] (rev.4, serial:0x20021102) at 0xb000, irq 16
1 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfb080000 irq 68

but the audigy, the one I use, doesn't come online.

Don't have a clue where to start to fix this.

help.
Thanks.

looks like a race condition between pipewire and Pulseaudio which appeared quite recently

Code: Select all

pulseaudio -k

should fix it.
If you are not using Wayland you can probably safely remove pipewire. Apparently version 3.13 of pipewire should have the problem fixed. For more info, see also https://bugs.launchpad.net/ubuntu/+sour ... ug/1897965

Thanks for answering.

But pulseaudio -k does not fix the issue, i get a "pop up" in middle of the screen saying "no output device"

Before I remove anything, what does pipewire do?

If it can help I've noticed when typing " cat /var/log/apt/term.log " and looking for today I see a few lines about pipewire:
Preparing to unpack .../161-pipewire_0.3.15-0xneon+20.04+focal+build5_amd64.deb ...
Unpacking pipewire:amd64 (0.3.15-0xneon+20.04+focal+build5) over (0.3.8-1+20.04+focal+build3) ...
Preparing to unpack .../162-pipewire-bin_0.3.15-0xneon+20.04+focal+build5_amd64.deb ...
Unpacking pipewire-bin (0.3.15-0xneon+20.04+focal+build5) over (0.3.8-1+20.04+focal+build3) ...
Preparing to unpack .../163-libpipewire-0.3-modules_0.3.15-0xneon+20.04+focal+build5_amd64.deb ...
Unpacking libpipewire-0.3-modules:amd64 (0.3.15-0xneon+20.04+focal+build5) over (0.3.8-1+20.04+focal+build3) ...
Preparing to unpack .../164-libpipewire-0.3-0_0.3.15-0xneon+20.04+focal+build5_amd64.deb ...
Unpacking libpipewire-0.3-0:amd64 (0.3.15-0xneon+20.04+focal+build5) over (0.3.8-1+20.04+focal+build3) ...

then further along:
Removed /etc/systemd/user/default.target.wants/pipewire.service.
Setting up libpipewire-0.3-0:amd64 (0.3.15-0xneon+20.04+focal+build5) ...
Setting up libpipewire-0.3-modules:amd64 (0.3.15-0xneon+20.04+focal+build5) ...
Setting up pipewire-bin (0.3.15-0xneon+20.04+focal+build5) ...
Installing new version of config file /etc/pipewire/pipewire.conf ...
Setting up pipewire:amd64 (0.3.15-0xneon+20.04+focal+build5) ...

Oh, then your problem is a different one, and you have a much newer Pipewire version than the one in the bugreport. As for pipewire's function: https://en.wikipedia.org/wiki/PipeWire

hello,

For completition/info the problem was debug/fixed on these links


https://bugs.kde.org/show_bug.cgi?id=429485
https://gitlab.freedesktop.org/pipewire ... issues/435
https://gitlab.freedesktop.org/pipewire ... issues/436