[SOLVED]Can't Pair Bluetooth Devices

[viejo]

This is a fairly fresh Debian install, only a few days I believe. I can't remember if bluetooth worked initially or not. If I try to pair a bluetooth device via Plasma's interface, I get the message "The setup of (bluetooth device) has failed".

Debian 11.2 Stable

lspci output:

Code: Select all

00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 11)
00:13.0 Serial controller: Intel Corporation Cannon Point-LP Integrated Sensor Hub (rev 11)
00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 11)
00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 11)
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 11)
00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 11)
00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 11)
00:16.3 Serial controller: Intel Corporation Cannon Point-LP Keyboard and Text (KT) Redirection (rev 11)
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 11)
00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f1)
00:1d.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #15 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 11)
00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11)
00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 11)
01:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
02:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
02:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
02:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
02:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
03:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] (rev 06)
37:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] (rev 06)
38:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
39:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
39:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] (rev 06)
6c:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
6d:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03)
6e:00.0 Non-Volatile memory controller: Intel Corporation Device 0975

If I check the service status of bluetooth by running sudo systemctl status bluetooth.service, it indicates an issue with something but I'm not sure exactly what this is saying. "Sap driver initialization failed", and "protocol not available".

Code: Select all

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-02-20 21:36:47 CST; 14min ago
       Docs: man:bluetoothd(8)
   Main PID: 1258 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18927)
     Memory: 4.0M
        CPU: 99ms
     CGroup: /system.slice/bluetooth.service
             └─1258 /usr/libexec/bluetooth/bluetoothd

Feb 20 21:36:47 Dragonfly bluetoothd[1258]: Bluetooth daemon 5.55
Feb 20 21:36:47 Dragonfly systemd[1]: Started Bluetooth service.
Feb 20 21:36:47 Dragonfly bluetoothd[1258]: Starting SDP server
Feb 20 21:36:47 Dragonfly bluetoothd[1258]: Bluetooth management interface 1.18 initialized
Feb 20 21:36:49 Dragonfly bluetoothd[1258]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Feb 20 21:36:49 Dragonfly bluetoothd[1258]: sap-server: Operation not permitted (1)
Feb 20 21:38:21 Dragonfly bluetoothd[1258]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 08:DF:1F:36:8F:F7: Protocol not available
Feb 20 21:39:11 Dragonfly bluetoothd[1258]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 08:DF:1F:36:8F:F7: Protocol not available
Feb 20 21:39:30 Dragonfly bluetoothd[1258]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 08:DF:1F:36:8F:F7: Protocol not available
Feb 20 21:48:04 Dragonfly bluetoothd[1258]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 04:5D:4B:C0:D9:6D: Protocol not available

Any ideas or insight is very much appreciated - Please let me know any additional info or output you'd like to see as well. Side note, but besides this bluetooth hiccup I'm loving Debian so far, and it has otherwise been my most stable Plasma experience thus far on this laptop/docking station combo.

Edit: I attempted to edit /etc/systemd/system/bluetooth.target.wants/bluetooth.service:

ExecStart=/usr/lib/bluetooth/bluetoothd
to
ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap

This got rid of the "Sap driver initialization failed" message on the bluetooth.service status, however I still get a protocol error as listed here, and bluetooth connection still fails with the same message in Plasma:

Code: Select all

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-02-20 22:00:28 CST; 1min 36s ago
       Docs: man:bluetoothd(8)
   Main PID: 852 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18927)
     Memory: 4.0M
        CPU: 52ms
     CGroup: /system.slice/bluetooth.service
             └─852 /usr/libexec/bluetooth/bluetoothd --noplugin=sap

Feb 20 22:00:28 Dragonfly systemd[1]: Starting Bluetooth service...
Feb 20 22:00:28 Dragonfly bluetoothd[852]: Bluetooth daemon 5.55
Feb 20 22:00:28 Dragonfly bluetoothd[852]: Starting SDP server
Feb 20 22:00:28 Dragonfly bluetoothd[852]: Excluding (cli) sap
Feb 20 22:00:28 Dragonfly systemd[1]: Started Bluetooth service.
Feb 20 22:00:28 Dragonfly bluetoothd[852]: Bluetooth management interface 1.18 initialized
Feb 20 22:01:37 Dragonfly bluetoothd[852]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 04:5D:4B:C0:D9:6D: Protocol not available

[FreewheelinFrank]

https://wiki.debian.org/BluetoothUser/a ... _available

[viejo]

https://wiki.debian.org/BluetoothUser/a ... _available

Installing the pulseaudio-module-bluetooth package and restarting the bluetooth service resolved this.

Thank you!

[barlafuss]

following, thanks

[sunrat]

https://wiki.debian.org/BluetoothUser/a ... _available

Installing the pulseaudio-module-bluetooth package and restarting the bluetooth service resolved this.

Thanks for posting the solution that worked for you. There have been several posts re bluetooth lately and this may help others. It would seem useful this package would be installed by default with other bluetooth packages as I would guess the main usage of bluetooth would be playing audio via PulseAudio.
It's amazing how many questions on the forum have solutions in the Debian Wiki!

[abu_bua]

As mentioned above the solution works for bullseye. For the sake of completion the commands:

Code: Select all

sudo apt-get install pulseaudio-module-bluetooth
pulseaudio --kill
pulseaudio --start

But keep in mind that pipewire breaks the a2dp chain. E.g. the headset will only play mono stuff and you cannot change the audio sink.

[seamusdemora]

https://wiki.debian.org/BluetoothUser/a ... _available

Installing the pulseaudio-module-bluetooth package and restarting the bluetooth service resolved this.

Thanks for posting the solution that worked for you. There have been several posts re bluetooth lately and this may help others. It would seem useful this package would be installed by default with other bluetooth packages as I would guess the main usage of bluetooth would be playing audio via PulseAudio.
It's amazing how many questions on the forum have solutions in the Debian Wiki!

This is ***so*** aggravating. One day it works - the next day it doesn't. The SAP thing "just disappeared" for a couple of days. I was still having issues with the reliability of the connection (it would run for 1-8 hours, but eventually failed, requiring a reboot to recover?!?), but it was working consistently with no SAP errors reported in 'systemctl status bluetooth.service'. Then, after a "reliability disconnect", it refuses to even connect to my speaker, and the systemd whining about SAP?! NOTHING CHANGED IN THE CONFIGURATION!!! grrrr.

[FreewheelinFrank]

This is ***so*** aggravating. One day it works - the next day it doesn't. The SAP thing "just disappeared" for a couple of days. I was still having issues with the reliability of the connection (it would run for 1-8 hours, but eventually failed, requiring a reboot to recover?!?), but it was working consistently with no SAP errors reported in 'systemctl status bluetooth.service'. Then, after a "reliability disconnect", it refuses to even connect to my speaker, and the systemd whining about SAP?! NOTHING CHANGED IN THE CONFIGURATION!!! grrrr.

Please start a new topic for your issue. This topic is old and the information may not apply, especially as you may well be running Bookworm rather than Bullseye. There has been a big change in some DEs switching to Pipewire. It would be worth searching the forum for more current topics that may affect you. Stating you Debian system details would help - version and DE. Also, please don't shout.

viewtopic.php?t=154544

[seamusdemora]

No - I am running Bullseye (Raspbian), and added `bullseye-backports` to my "sources" recently.

But yeah - I'll leave.