Comment # 2 on bug 1208783 from
When I start up my X session, pulseaudio is usually running and jackdbus, but
neither connected to the hardware. I usually see the issue when I run
"jack_control start" to start jack (which then bridges to pulse audio). Or if I
stop the jack server or kill jackdbus (which sometimes hangs).

What I just noticed is that pipewire was also running in the background. I was
not even aware that I had it running on this system and strange because usually
pipewire and pulse do not play well together. I have disabled the pipewire
service now and will see if the issue seems to go away.

But if you need me to reproduce let me know.


You are receiving this mail because: