Bug#1091358: mumble: crashes on startup with pipewire backtrace
Philipp Kern
pkern at debian.org
Thu Jan 2 16:32:47 GMT 2025
Control: tag -1 - unreproducible
Hi,
On 1/1/25 7:47 AM, Chris Knadle wrote:
> A further clue is that there's an error of file client.conf missing. I
> searched the VM running mumble and it looks like it should be:
>
> /usr/share/pipewire/client.conf
>
> That should be in the 'pipewire-bin' package, which the 'pipewire'
> package depends on. Please do a quick check that these two packages are
> installed locally. [If you're running pipewire I can't imagine either of
> these wouldn't be installed.]
Looks like this dependency/recommends is missing then. mumble indeed
starts if pipewire-bin is installed, which is not a dependency on
anything in KDE, nor by mumble itself.
I installed these packages:
> Installing:
> pipewire-bin
>
> Installing dependencies:
> libconfig++9v5 libglibmm-2.4-1t64 libpipewire-0.3-modules libsigc++-2.0-0v5 libxml++2.6-2v5 pipewire-pulse
> libffado2 libopenfec1 libroc0.4 libwireplumber-0.5-0 pipewire wireplumber
Then it worked. This seems to imply that there is something broken in
mumble where it loads the pipewire library that is installed but fails
because the config is not there?
When I remove pipewire-bin, it removes these:
> REMOVING:
> pipewire pipewire-bin pipewire-pulse wireplumber
When I then delete ~/.config/Mumble it segfaults again. With it already
created, it starts.
When I remove pipewire-bin and call mumble with the config already
created, it segfaults on exit. (I have not tried actually connecting to
a server and doing the talking.)
> The other thing I notice are strange directories, such as ./src/mumble/
> PipeWire.cpp. Is this crash the result of running mumble from a local
> build, rather than from the binary Debian package?
No, I used debuginfod.debian.net, but it was from the package.
Kind regards
Philipp Kern
More information about the Pkg-voip-maintainers
mailing list