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

Code: Select all

pulseaudio -k

should fix it.

Well that worked for me, but the issue repeated when I reboot the kubuntu.
What could it be?

Currently running Kubuntu 20.10, Plasma 5.19.5, Kernel: 5.8.0-29, NVIDIA-SMI 455.45.01

alekspickle wrote:
Well that worked for me, but the issue repeated when I reboot the kubuntu.
What could it be?

Currently running Kubuntu 20.10, Plasma 5.19.5, Kernel: 5.8.0-29, NVIDIA-SMI 455.45.01

The solution I mentioned above, it just doesn't apply to Neon apparently as they have a newer pipewire package.

In short: remove pipewire (unless you use Wayland where you need it)

Mamarok wrote:
In short: remove pipewire (unless you use Wayland where you need it)

Sorry for my stupidity, but I dont even know whether I need it or not...I just installed kubuntu 20.10 and this keeps happening.
I did not know what Wayland is until right about now. I assume Wayland is far from ready and I definitely using Xserver now.

So should I just do

Code: Select all

sudo apt remove pipewire
sudo apt-get purge pipewire*

?

Mamarok wrote: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

That is what I wrote, not really hard to understand IMO... and if you were using Wayland you would know, as it is not the default UI

FWIW: you are hijacking a Neon thread btw... Splitting the posts now for better use