Reply to topic

no audio output device found after todays update 2020-11-20

milikitato
Registered Member
Posts
33
Karma
0
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.
User avatar Mamarok
Manager
Posts
5180
Karma
15
OS
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


Currently running Kubuntu 20.10, Plasma 5.19.5, Frameworks 5.74.0, Qt 5.14.2, kernel 5.8.0-29, AMD RENOiR Graphics
FWIW: it is always useful to state the exact Plasma version and distribution when asking questions, makes it easier for us to help ...
milikitato
Registered Member
Posts
33
Karma
0
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) ...
User avatar Mamarok
Manager
Posts
5180
Karma
15
OS
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


Currently running Kubuntu 20.10, Plasma 5.19.5, Frameworks 5.74.0, Qt 5.14.2, kernel 5.8.0-29, AMD RENOiR Graphics
FWIW: it is always useful to state the exact Plasma version and distribution when asking questions, makes it easier for us to help ...

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], Google [Bot], rtokumori, Sogou [Bot], YaCy [Bot]