You are not logged in.

#1 2020-06-21 22:40:02

minifridge
Member
Registered: 2020-06-21
Posts: 3

[SOLVED] Bluetooth headset is not registered in pulseaudio

Hi,

I am a new arch user and I have some trouble detecting my bluetooth receiver with pulseaudio.

The bluetooth was working flawlessly up until today when I set it up as a default sink:

#/etc/pulse/default.pa
set-default-sink  bluez_sink.40_ED_98_19_8F_1A.a2dp_sink

Now pulseaudio can not detect the device at all!

$ pactl list short
0	module-device-restore		
1	module-stream-restore		
2	module-card-restore		
3	module-augment-properties		
4	module-switch-on-port-available		
5	module-switch-on-connect		
6	module-udev-detect		
7	module-alsa-card	device_id="2" name="usb-FX-AUDIO_FX-AUDIO-DAC-X6-00" card_name="alsa_card.usb-FX-AUDIO_FX-AUDIO-DAC-X6-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1"	
8	module-alsa-card	device_id="1" name="usb-Generic_USB_Audio_200901010001-00" card_name="alsa_card.usb-Generic_USB_Audio_200901010001-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1"	
9	module-alsa-card	device_id="0" name="pci-0000_00_1f.3" card_name="alsa_card.pci-0000_00_1f.3" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1"	
10	module-bluetooth-policy	auto_switch=2	
11	module-bluetooth-discover		
12	module-bluez5-discover		
13	module-dbus-protocol		
14	module-native-protocol-unix		
15	module-gsettings		
16	module-default-device-restore		
17	module-rescue-streams		
18	module-always-sink		
19	module-intended-roles		
20	module-console-kit		
21	module-systemd-login		
22	module-position-event-sounds		
23	module-role-cork		
24	module-filter-heuristics		
25	module-filter-apply		
0	alsa_output.usb-FX-AUDIO_FX-AUDIO-DAC-X6-00.analog-stereo	module-alsa-card.c	s16le 2ch 44100Hz	IDLE
1	alsa_output.usb-Generic_USB_Audio_200901010001-00.HiFi__hw_Dock_1__sink	module-alsa-card.c	s24le 2ch 48000Hz	IDLE
2	alsa_output.usb-Generic_USB_Audio_200901010001-00.HiFi__hw_Dock__sink	module-alsa-card.c	s24le 2ch 48000Hz	IDLE
3	alsa_output.pci-0000_00_1f.3.analog-stereo	module-alsa-card.c	s16le 2ch 44100Hz	IDLE
0	alsa_output.usb-FX-AUDIO_FX-AUDIO-DAC-X6-00.analog-stereo.monitor	module-alsa-card.c	s16le 2ch 44100Hz	RUNNING
1	alsa_output.usb-Generic_USB_Audio_200901010001-00.HiFi__hw_Dock_1__sink.monitor	module-alsa-card.c	s24le 2ch 48000Hz	IDLE
2	alsa_output.usb-Generic_USB_Audio_200901010001-00.HiFi__hw_Dock__sink.monitor	module-alsa-card.c	s24le 2ch 48000Hz	IDLE
3	alsa_input.usb-Generic_USB_Audio_200901010001-00.HiFi__hw_Dock__source	module-alsa-card.c	s24le 2ch 48000Hz	RUNNING
4	alsa_output.pci-0000_00_1f.3.analog-stereo.monitor	module-alsa-card.c	s16le 2ch 44100Hz	IDLE
5	alsa_input.pci-0000_00_1f.3.analog-stereo	module-alsa-card.c	s16le 2ch 44100Hz	IDLE
1	3	7	protocol-native.c	float32le 1ch 25Hz
3	0	7	protocol-native.c	float32le 1ch 25Hz
0	module-systemd-login.c	(null)
1	protocol-native.c	gnome-shell
3	protocol-native.c	gsd-media-keys
4	protocol-native.c	gnome-pomodoro
5	protocol-native.c	gnome-pomodoro
6	protocol-native.c	insync
7	protocol-native.c	gnome-control-center
8	protocol-native.c	firefox
9	protocol-native.c	gnome-shell
10	protocol-native.c	firefox
11	protocol-native.c	pactl
0	bell-window-system	s16le 2ch 44100Hz	0.752
0	alsa_card.usb-FX-AUDIO_FX-AUDIO-DAC-X6-00	module-alsa-card.c
1	alsa_card.usb-Generic_USB_Audio_200901010001-00	module-alsa-card.c
2	alsa_card.pci-0000_00_1f.3	module-alsa-card.c

From my what I can understand in the udev monitor and the journalctl the device is recognized as keyboard input device and not as an audio sink?

# journalctl -b
Jun 21 23:31:57 minifridge pipewire[1123]: [E][000002060.617711][media-session.c:1071 create_object()] media-session 0x7ffea0228150: unknown object type PipeWire:Interface:ClientNode
Jun 21 23:31:57 minifridge kernel: input: FiiO BTR3 (AVRCP) as /devices/virtual/input/input47
Jun 21 23:31:57 minifridge systemd-logind[456]: Watching system buttons on /dev/input/event256 (FiiO BTR3 (AVRCP))
KERNEL[900.318123] remove   /devices/virtual/input/input43/event256 (input)
UDEV  [900.321946] remove   /devices/virtual/input/input43/event256 (input)
KERNEL[900.352646] remove   /devices/virtual/input/input43 (input)
UDEV  [900.353452] remove   /devices/virtual/input/input43 (input)
KERNEL[904.768250] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256 (bluetooth)
UDEV  [904.773196] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256 (bluetooth)
KERNEL[909.794711] add      /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256 (bluetooth)
UDEV  [909.800646] add      /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256 (bluetooth)
KERNEL[910.144277] add      /devices/virtual/input/input44 (input)
KERNEL[910.144393] add      /devices/virtual/input/input44/event256 (input)
UDEV  [910.147759] add      /devices/virtual/input/input44 (input)
UDEV  [910.225361] add      /devices/virtual/input/input44/event256 (input)

I was using the LDAC codes and I can confirm that another bluetooth speaker I tested was recognized with no problems by pulse audio. I have no idea why this happened in the first case. Currently, the media buttons on the receiver work when it is paired but no sound functionality.

Possible solutions workarounds I would like help with:
1- Is there a way, like a udev rule which I can force this device to be recognized by pulseaudio?
2- Is there a way to reset everything and try again?

Last edited by minifridge (2020-06-26 00:32:05)

Offline

#2 2020-06-26 00:29:52

minifridge
Member
Registered: 2020-06-21
Posts: 3

Re: [SOLVED] Bluetooth headset is not registered in pulseaudio

I found some error logged in the bluetooth service:

Jun 26 01:04:20 minifridge bluetoothd[459]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Jun 26 01:04:20 minifridge bluetoothd[459]: RFCOMM server failed for :1.110/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb: rfcomm_bind: Address already in use (98)
Jun 26 01:10:18 minifridge bluetoothd[459]: Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

Using this stackexchange resource The following commands fixed it:

$ sudo rfkill block bluetooth
$ sudo rfkill unblock bluetooth
$ sudo systemctl restart bluetooth

Offline

Board footer

Powered by FluxBB