Mumble disables my Bluetooth headset

[Arthur-D]

Description

Whenever I start Mumble, my Bluetooth headset gets disabled system-wide.
It also applies whenever I have Mumble open first and then connect the headset, it connects but gets disabled as a playback device system-wide.
I can easily enable it again in my system sound settings, but it is rather annoying, and strange.

Steps to reproduce

1. Connect Bluetooth headset.
2. Start Mumble.
3. See Bluetooth headset get disabled as playback device system-wide.
   OR
4. Start Mumble.
5. Connect Bluetooth headset.
6. See Bluetooth headset is disabled as playback device system-wide.

Mumble version

1.4.287

Mumble component

Client

OS

Linux

Reproducible?

Yes

Additional information

I am using OpenSUSE Tumbleweed, with PipeWire as sound server, under KDE Plasma. Mumble is installed as a Flatpak, though I don't know if that would really change anything in this case.

My Bluetooth headset is a Sony WH-XB910N, and if I don't have Mumble open, it gets set as default playback device as it should whenever I connect it. For the record, I have not found any other application messing with my system-wide playback like Mumble does, which is why I am filing this bug here.

Relevant log output

No response

Screenshots

This is what happens whenever Mumble is open:

Luckily, I can still enable it after the fact, Mumble doesn't hinder that, but the fact that it disables my Bluetooth headset has been going on for about a year now I think. This is how it should be:

[Krzmbrzl]

Do you have the Exclusive Checkbox checked in the audio input and/or output settings?

[Arthur-D]

No, in fact that checkbox is greyed out for me in both Audio Input and Audio Output settings for Mumble.
Like this:

(Also that is an amazingly quick response time, thanks for getting back to me.)

[davidebeatrici]

Does journalctl tell something related?

[Arthur-D]

I'm not sure, but maybe this is related? Doesn't really say anything about cause, but maybe it's something.

And:

[davidebeatrici]

Yep, looks like the PipeWire node goes into error...

[Arthur-D]

Is there something else I can do to help debug this? Or is this something that's not really a Mumble bug? Thank you very much for your time.

[Krzmbrzl]

It's likely a bug in our PipeWire implementation somehow. @davidebeatrici knows this best, so he might know what could be important here.