Bluetooth audio devices not available consistently

English Multimedia
1

Bluetooth audio has not been working consistently for several weeks. It’s not something I use regularly, so I’m not sure when it last worked, but I’d guess about 3-4 weeks ago.

My Bluetooth audio devices successfully connect and show up in the Bluetooth panel as active. However, they often do not appear as an available audio device. Sometimes, restarting Bluetooth fixes the issue.

Any idea what is causing the initial failures or how I can troubleshoot this further? Currently running Tumbleweed-20220226, KDE. Hardware is a Thinkpad T14s.

On boot, I get “Address already in use” and “Host is down”:


[FONT=monospace]Feb 27 11:33:46 systemd[1]: Starting Bluetooth service... 
Feb 27 11:33:46 bluetoothd[1769]: Bluetooth daemon 5.62 
Feb 27 11:33:46 systemd[1]: Started Bluetooth service. 
Feb 27 11:33:46 bluetoothd[1769]: Starting SDP server 
Feb 27 11:33:46 bluetoothd[1769]: Bluetooth management interface 1.21 initialized 
Feb 27 11:33:46 bluetoothd[1769]: Admin Policy Set interface registered 
Feb 27 11:33:46 bluetoothd[1769]: Admin Policy Status interface registered 
Feb 27 11:34:48 bluetoothd[1769]: Player registered: sender=:1.93 path=/media_player0 
Feb 27 11:34:48 bluetoothd[1769]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/ldac 
Feb 27 11:34:48 bluetoothd[1769]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/aac 
Feb 27 11:34:48 bluetoothd[1769]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSink/sbc 
Feb 27 11:34:48 bluetoothd[1769]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/sbc 
Feb 27 11:34:48 bluetoothd[1769]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSink/sbc_xq 
Feb 27 11:34:48 bluetoothd[1769]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/sbc_xq 
Feb 27 11:34:48 bluetoothd[1769]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/faststream 
Feb 27 11:34:48 bluetoothd[1769]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/faststream_duplex 
Feb 27 11:34:51 bluetoothd[1769]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already  
in use (98) 
Feb 27 11:34:51 bluetoothd[1769]: src/profile.c:ext_start_servers() RFCOMM server failed for Hands-Free Voice gateway: rfcomm_bind:      
Address already in use (98) 
Feb 27 11:34:51 bluetoothd[1769]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSink/sbc 
Feb 27 11:34:51 bluetoothd[1769]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSource/sbc 
Feb 27 11:34:51 bluetoothd[1769]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSink/sbc_xq_453 
Feb 27 11:34:51 bluetoothd[1769]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSource/sbc_xq_453 
Feb 27 11:34:51 bluetoothd[1769]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSink/sbc_xq_512 
Feb 27 11:34:51 bluetoothd[1769]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSource/sbc_xq_512 
Feb 27 11:34:51 bluetoothd[1769]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSink/sbc_xq_552 
Feb 27 11:34:51 bluetoothd[1769]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSource/sbc_xq_552 
Feb 27 11:34:55 bluetoothd[1769]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down 
Feb 27 11:35:00 bluetoothd[1769]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
[/FONT]

Subsequently connecting a device shows “Device or resource busy” and “Transport endpoint is not connected”:


Feb 28 08:14:28 bluetoothd[1769]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 38:F3:2E:D2:5C:EB:   
Device or resource busy 
Feb 28 08:14:29 bluetoothd[1769]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 38:F3:2E:D2:5C:EB:   
Device or resource busy 
Feb 28 08:14:56 bluetoothd[1769]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway:       
getpeername: Transport endpoint is not connected (107) 
Feb 28 08:14:56 bluetoothd[1769]: profiles/audio/avdtp.c:avdtp_sep_set_state() Error changing sep state: stream not available

Restarting Bluetooth looks very similar, same errors:


Feb 28 09:06:05 systemd[1]: Starting Bluetooth service... 
Feb 28 09:06:05 bluetoothd[21539]: Bluetooth daemon 5.62 
Feb 28 09:06:05 systemd[1]: Started Bluetooth service. 
Feb 28 09:06:05 bluetoothd[21539]: Starting SDP server 
Feb 28 09:06:05 bluetoothd[21539]: Bluetooth management interface 1.21 initialized 
Feb 28 09:06:05 bluetoothd[21539]: Admin Policy Set interface registered 
Feb 28 09:06:05 bluetoothd[21539]: Admin Policy Status interface registered 
Feb 28 09:06:05 bluetoothd[21539]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already 
in use (98) 
Feb 28 09:06:05 bluetoothd[21539]: src/profile.c:ext_start_servers() RFCOMM server failed for Hands-Free Voice gateway: rfcomm_bind:     
Address already in use (98) 
Feb 28 09:06:05 bluetoothd[21539]: Player registered: sender=:1.93 path=/media_player2 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSink/sbc 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSource/sbc 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSink/sbc_xq_453 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSource/sbc_xq_453 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSink/sbc_xq_512 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSource/sbc_xq_512 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSink/sbc_xq_552 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.112 path=/MediaEndpoint/A2DPSource/sbc_xq_552 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/ldac 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/aac 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSink/sbc 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/sbc 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSink/sbc_xq 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/sbc_xq 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/faststream 
Feb 28 09:06:05 bluetoothd[21539]: Endpoint registered: sender=:1.93 path=/MediaEndpoint/A2DPSource/faststream_duplex 
Feb 28 09:06:12 bluetoothd[21539]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down 
Feb 28 09:06:18 bluetoothd[21539]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down

This time, connecting a device, there’s still “Device or resource busy,” but then “ready,” and now it works.


Feb 28 09:10:34 bluetoothd[21539]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 38:F3:2E:D2:5C:EB: Device or 
resource busy 
Feb 28 09:10:35 bluetoothd[21539]: /org/bluez/hci0/dev_38_F3_2E_D2_5C_EB/fd0: fd(30) ready
2

I had the same problem a few days ago, and seems now it’s fixed with the latest update.

3

I have the same problem from Sep 14, 2022

4

I managed to make it work after issuing restart command : systemctl restart bluetooth.service

5

Thanks for that! Yeah that works for me too - my (rude) workaround was: sudo zypper in -f bluez (ahem)

6

Same problem here (2022_10_16 kernel 6.0.2), same solution: sudo systemctl restart bluetooth.service.

7

Restarting the service worked for me as well on 20221021 TW

8

Thankfully I have not encounter problem with bluetooth in tumbleweed.
In yast2 system services I make it sure to start it at boot, like in systemctl but this one a gui.:wink:
Just wondering if you guys install the bluetooth mesh also. I always have it on my machine.

9

I had the same problem (with Linux Mint, not Suse, but I doubt if that makes any difference; there are reports for Arch Linux too), and found this super simple solution:

Just make sure the batteries are properly charged!

The longer story: Wireless earbuds for Linux Mint

10

My message was marked as spam (then released anyway). I strongly disagree with that, it is counterproductive. I was honestly only trying to help people finding this topic.

A recognisable mishandling of the situation, it has happened before elsewhere:

11

The forum software allows any user to flag a message. But that send a report to moderators.

In your case, a user flagged it as spam, but a moderator cleared it to be seen.

All Internet forum have to deal with forum spammers, and sometimes they initially get it wrong.

Welcome to our forum. Apologies for the unhappy experience.

1 Like
12

I have exactly the same issue on my Tumbleweed with various bluetooth audio devices and various bluetooth hosts, both PCI cards and USB cards, either BT 4.2 or BT 5.0.
Also, there is a bug report (1210748 – Bluetooth audio is not working after a reboot). I would help if you comment/add your email to the CC list so as developers realize that this is more common than they believe/think/etc.

FYI, my issue is happening only on Tumbleweed which is on my desktop. My laptop(s) have Fedora 36/37 and have no issue, obviously I have checked with the same PCI cards.

1 Like