This is definitely a bug and one we need to solve before the masses start using jammy. So just closing it wouldn't be helpful.
I'm reminded a little of bug 1897965. Maybe we need either:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1897965/comments/16
or to modify pipewire-media-session.service with something like:
/usr/bin/pipewire-media-session -d bluez5,alsa-seq,alsa-pcm,alsa-acp
That way PulseAudio is always the only one trying to control the hardware.
Alternatively; don't install pipewire-media-session by default. So long as it's not needed for Wayland screencasting/recording like at least some of Pipewire is :S
This is definitely a bug and one we need to solve before the masses start using jammy. So just closing it wouldn't be helpful.
I'm reminded a little of bug 1897965. Maybe we need either:
https:/ /bugs.launchpad .net/ubuntu/ +source/ pipewire/ +bug/1897965/ comments/ 16
or to modify pipewire- media-session. service with something like:
/usr/ bin/pipewire- media-session -d bluez5, alsa-seq, alsa-pcm, alsa-acp
That way PulseAudio is always the only one trying to control the hardware.
Alternatively; don't install pipewire- media-session by default. So long as it's not needed for Wayland screencasting/ recording like at least some of Pipewire is :S