Murmure version
1.10.1
Operating system
Linux
Display server (Linux only)
Wayland
Linux distribution (Linux only)
Nobara 44
Feature impacted
Transcription
Bug description
On Linux (PipeWire), a Bluetooth headset's microphone (Google Pixel Buds Pro 2) never appears in the Settings → System → Microphone dropdown, even though the system correctly exposes it and it works fine in other applications.
Regular ALSA microphones (USB headset, webcam) show up normally in Murmure — only the bluez_input.* source type seems to be missing from the list, while alsa_input.* sources are detected without issue.
Expected: active Bluetooth sources (HSP/HFP profile) should appear in the microphone list alongside ALSA sources.
Steps to reproduce
- Connect a Bluetooth headset with microphone support (tested with Google Pixel Buds Pro 2)
- Ensure the active PipeWire profile is headset-head-unit (HSP/HFP), not A2DP — confirmed via
pactl list cards
- Open Murmure → Settings → System → Microphone
- Click the refresh icon (↻)
- See error: the Bluetooth device never appears in the dropdown, only ALSA devices (USB, built-in) are listed
Also tested without success:
- Restarting the app completely
- Disconnecting/reconnecting Bluetooth
- Raising mic input volume to 100% (was 37% by default)
- Setting the Bluetooth source as the system default (
pactl set-default-source bluez_input...)
Confirmed working at the system level:
$ pactl list sources short
106 bluez_input.XX:XX:XX:XX:XX:XX PipeWire float32le 1ch 48000Hz RUNNING
$ pactl list cards
Card #103
device.description = "Pixel Buds Pro 2"
Active Profile: headset-head-unit (HSP/HFP, codec LC3-SWB)
Ports: headset-input (Mains-libres), sources: 1
$ parecord --device=bluez_input.XX:XX:XX:XX:XX:XX test.wav
→ clean, clear audio on playback (paplay test.wav)
This suggests Murmure's microphone enumeration filters out or ignores PipeWire sources prefixed bluez_input.*, while alsa_input.* sources are correctly detected.****
Debug logs
Murmure version
1.10.1
Operating system
Linux
Display server (Linux only)
Wayland
Linux distribution (Linux only)
Nobara 44
Feature impacted
Transcription
Bug description
On Linux (PipeWire), a Bluetooth headset's microphone (Google Pixel Buds Pro 2) never appears in the Settings → System → Microphone dropdown, even though the system correctly exposes it and it works fine in other applications.
Regular ALSA microphones (USB headset, webcam) show up normally in Murmure — only the
bluez_input.*source type seems to be missing from the list, whilealsa_input.*sources are detected without issue.Expected: active Bluetooth sources (HSP/HFP profile) should appear in the microphone list alongside ALSA sources.
Steps to reproduce
pactl list cardsAlso tested without success:
pactl set-default-source bluez_input...)Confirmed working at the system level:
$ pactl list sources short
106 bluez_input.XX:XX:XX:XX:XX:XX PipeWire float32le 1ch 48000Hz RUNNING
$ pactl list cards
Card #103
device.description = "Pixel Buds Pro 2"
Active Profile: headset-head-unit (HSP/HFP, codec LC3-SWB)
Ports: headset-input (Mains-libres), sources: 1
$ parecord --device=bluez_input.XX:XX:XX:XX:XX:XX test.wav
→ clean, clear audio on playback (paplay test.wav)
This suggests Murmure's microphone enumeration filters out or ignores PipeWire sources prefixed
bluez_input.*, whilealsa_input.*sources are correctly detected.****Debug logs