Description of problem: I have a pair of Jabra Elite 45h headphones that was working just fine until I updated to Fedora 33. When I try to pair via bluetoothctl I get the following error [bluetooth]# pair 70:BF:92:D6:51:CB Attempting to pair with 70:BF:92:D6:51:CB [CHG] Device 70:BF:92:D6:51:CB Connected: yes Failed to pair: org.bluez.Error.AuthenticationFailed [CHG] Device 70:BF:92:D6:51:CB Connected: no when I try to pair via the GUI I get bluetoothd[8275]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 70:BF:92:D6:51:CB: Connection refused (111) Version-Release number of selected component (if applicable): luez-5.55-1.fc3 How reproducible: 100% Steps to Reproduce: 1. Try to pair 2. 3. Additional info: > https://fedoraproject.org/wiki/How_to_debug_Bluetooth_problems Using this as a guideline I see the following errors lsusb -v | grep Bluetooth | grep DeviceProtocol can't get debug descriptor: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable can't get device qualifier: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable can't get device qualifier: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable can't get device qualifier: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable can't get device qualifier: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable bDeviceProtocol 1 Bluetooth and in the systemtab status Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource/sbc Endpoint registered: sender=:1.70 path=/MediaEndpoint/A2DPSink/sbc Endpoint registered: sender=:1.70 path=/MediaEndpoint/A2DPSource/sbc src/profile.c:ext_start_servers() RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already in use (98) Endpoint unregistered: sender=:1.70 path=/MediaEndpoint/A2DPSink/sbc Endpoint unregistered: sender=:1.70 path=/MediaEndpoint/A2DPSource/sbc src/profile.c:ext_connect() Headset Voice gateway failed connect to 70:BF:92:D6:51:CB: Connection refused (111) profiles/audio/avdtp.c:avdtp_connect_cb() connect to 70:BF:92:D6:51:CB: Connection refused (111) profiles/audio/avdtp.c:avdtp_connect_cb() connect to 70:BF:92:D6:51:CB: Connection refused (111)
Its a kernel problem... On the 5-9 kernel I tried bluez-5.53, bluez-5.54, bluez-5.5 all failed with Connection refused (111) Then I tried bluez-5.5 on the last 5.8 kernel (5.8.18-300.fc33)... everything worked again! Should the component be changed?
> Its a kernel problem... On the 5-9 kernel I tried Bluetooth is complex, it could be firmware, kernel, bluez, controller, end device or a combination of them all. > Then I tried bluez-5.5 on the last 5.8 kernel I'm guessing you mean 5.55 > Should the component be changed? It looks a lot like this problem and it looks like on that thread there's means of work around but there doesn't appear to be a final consensus to the problem. Kernel is likely the best spot to track it. Can you please include details of the actual bluetooth controller too please.
> It looks a lot like this problem and it looks like on that thread there's https://www.spinics.net/lists/linux-bluetooth/msg88074.html
(In reply to Peter Robinson from comment #2) > > Its a kernel problem... On the 5-9 kernel I tried > > Bluetooth is complex, it could be firmware, kernel, bluez, controller, end > device or a combination of them all. > > > Then I tried bluez-5.5 on the last 5.8 kernel > > I'm guessing you mean 5.55 Yes... The latest bits. > > > Should the component be changed? > > It looks a lot like this problem and it looks like on that thread there's > means of work around but there doesn't appear to be a final consensus to the > problem. Kernel is likely the best spot to track it. Can you please include > details of the actual bluetooth controller too please. # hciconfig hci0: Type: Primary Bus: USB BD Address: 04:D3:B0:C5:59:B7 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:33428052 acl:386 sco:654485 events:4614 errors:0 TX bytes:34180724 acl:626 sco:653750 commands:3366 errors:0 [bluetooth]# show Controller 04:D3:B0:C5:59:B7 (public) Name: madhat.boston.devel.redhat.com Alias: madhat.boston.devel.redhat.com Class: 0x003c010c Powered: yes Discoverable: yes DiscoverableTimeout: 0x00000000 Pairable: yes UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb) UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb) UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0537 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x05 (5) SupportedIncludes: appearance SupportedIncludes: local-name Hopefully is is what you are looking for if not please let me know. And I'm more than willing to test any new bits you come up with.
(In reply to Peter Robinson from comment #3) > > It looks a lot like this problem and it looks like on that thread there's > > https://www.spinics.net/lists/linux-bluetooth/msg88074.html Well... this patch does not apply to a kernel-5.9.13-200.fc33 but does apply cleanly to a kernel-5.10.0-0.rc7.93.fc34. So it is not clear how that patch can help a 5.9 kernel.
> Hopefully is is what you are looking for if not please let me know. More a lspci/lsusb to output make/model details.
(In reply to Peter Robinson from comment #6) > > Hopefully is is what you are looking for if not please let me know. > > More a lspci/lsusb to output make/model details. # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:16.3 Serial controller: Intel Corporation Sunrise Point-LP Active Management Technology - SOL (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.6 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21) 04:00.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01) 05:00.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01) 05:01.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01) 05:02.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01) 06:00.0 System peripheral: Intel Corporation JHL6240 Thunderbolt 3 NHI (Low Power) [Alpine Ridge LP 2016] (rev 01) 07:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 08:01.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02) 09:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018 / PC SN720 NVMe SSD 3d:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 3e:00.0 Non-Volatile memory controller: Lenovo Device 0003 # lsusb Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 1050:0010 Yubico.com Yubikey (v1 or v2) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
(In reply to Peter Robinson from comment #3) > > It looks a lot like this problem and it looks like on that thread there's > > https://www.spinics.net/lists/linux-bluetooth/msg88074.html I did some testing with different Fedora kernels and here is what I found. kenrel-5.8.18-300.fc33 => bluetooth worked kernel-5.10.0-0.rc7.93.fc34 => bluetooth worked kernel-5.10.0-0.rc7.93.fc34 (w/ the above patch) => bluetooth worked kernel-5.9.13-200.fc33 => did not work kernel-5.9.13-100.fc33 => did not work All the testing was done with the 5.55 version of bluez So this is definitely a 5.9 kernel problem.
> So this is definitely a 5.9 kernel problem. I have the exact same bluetooth controller in a ThinkPad X1 Carbon Gen 6 and bluetooth with a mouse and my BOSE headphones works fine with the 5.9.13 kernel so I think it's more "A 5.9 kernel problem with certain hardware". God I hate bluetooth, so many standards, so many moving parts :( Let me see if I can work out what fixed it in 5.10
I believe this should be fixed now with the latest kernel/bluez, can you confirm?
(In reply to Peter Robinson from comment #10) > I believe this should be fixed now with the latest kernel/bluez, can you > confirm? It is... I'll close the bug...