tags 1091358 + help
thanks
This bug seems to be triggered by a missing dependency on package
pipewire-bin which contains /usr/share/pipewire/client.conf
configuration needed to use pipewire.
It is not clear where the dependency needs to be added; adding it to
Mumble does not seem to make sense as it can use several audio backends.
Thanks
-- Chris
Chris Knadle
chris.kna...@coredump.us
On 1/2/25 13:47, Chris Knadle wrote:
Hello Phillip.
The 'recommends' alternatives would need to include pipewire, pulse,
jack, and ALSA, (Mumble has supported all of these), and not sure what
else. And because of that I think the recommends wouldn't work,
because pulseaudio alone would satisfy the recommends, which I believe
is the situation here.
I've looked at the build dependencies for the newer Mumble and it also
doesn't include any dependencies on pipewire.
https://github.com/mumble-voip/mumble/blob/master/docs/dev/build-instructions/build_linux.md
I was going to say pipewire should have a dependency on pipewire-bin
-- but it already does. Pipewire-pulse, though, does not have a
dependency on pipewire-bin. So maybe that's what's going on -- that
pulse is the only audio backend in use, with a pipewire compatibility
which doesn't load the pipewire configuration package because it's not
actually in use. A few months ago I was using a Debian system running
pulse with pipewire-pulse loaded and not pipewire, and I was having
audio problems. I ended up having to switch to pipewire "wholesale" to
get audio working well, because at the time I remember pulseaudio and
pipewire conflicting.
Now looking at my local system I'm a bit more confused, because
several VMs I'm using have pipewire as well as pulseaudio loaded at
the same time.
However given the difficulty run into with this bug, I can sort of see
why running both would be needed.
It feels like we need more information and more discussion with those
more familiar with audio libraries and dependencies to get somewhere
with this.
-- Chris
Chris Knadle
chris.kna...@coredump.us
