Bug#1107868: mumble: segfault on first start

[Thorsten Glaser]

On Sat, 21 Jun 2025, Chris Knadle wrote:

> The ALSA backend is supported, and depends on it, and loads other audio
> libraries if they are found (PipeWire, PulseAudio, JACK) -- but if PipeWire is
> found it prioritizes that over ALSA. So in this case it looks like
> libpipewire-0.3.so.0 and libpulse.so.0 are found, so Mumble tries to connect to
> pipewire, but then the PipeWire configuration pw.conf isn't found, leading to a
> Segfault.

Heh.

Presence of the client libraries must not be used as an indicator
that the thing is used. The client libraries are there because some
software links against them to support these things, no matter whether
they actually are used, after all (mplayer most likely). This is like
with libsystemd0 which is present so dæmons can use it to communicate
with systemd about their readiness state, so the dæmon executable is
linked against it, but it’s never actually used on my system since there
is no systemd on it. (Other than being used as entry door for the Jia Tan
exploit, of course.)

> Upsgream would like to fix the bug and they are requesting a coredump and/or a
> backtrace, if that can be provided.

I can provide a backtrace (just not right now) easily enough. Not sure
about a coredump vs. possible info leak, will have to see.

Later,
//mirabilos
-- 
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)