Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1060795: bluez: Troubles with bluetooth after upgrade from bookworm to testing (trixie): br-connection-unknown

42 views
Skip to first unread message

Chris Joelly

unread,
Jan 14, 2024, 6:10:05 AM1/14/24
to
Package: bluez
Version: 5.71-1
Severity: important

Since the upgrade to testing, the following happens when connecting to a bt
headset:

* Not paired, not trusted: can pair and trust and use the device.
* When disconnecting, rebooting the machine, connection to bt device fails with
'br-connection-unknown'
* After removing the bt device again and re-pair, it is possible to connect to
it again.

Further info: I am using pipewire instead of pulseaudio.

Following a transscript of a session with the error and how to fix it:

user@laptop1:~$ bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# devices
Device 8C:57:9B:18:C3:A7 h.ear go (SRS-HG1)
Device 60:AB:D2:43:BB:9C Bose QC35 II
[bluetooth]# connect 60:AB:D2:43:BB:9C
Attempting to connect to 60:AB:D2:43:BB:9C
[CHG] Device 60:AB:D2:43:BB:9C Connected: yes
[Bose QC35 II]# Failed to connect: org.bluez.Error.Failed br-connection-unknown
[CHG] Device 60:AB:D2:43:BB:9C Connected: no
[bluetooth]# info 60:AB:D2:43:BB:9C
Device 60:AB:D2:43:BB:9C (public)
Name: Bose QC35 II
Alias: Bose QC35 II
Class: 0x00240418 (2360344)
Icon: audio-headphones
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Vendor specific (00000000-deca-fade-deca-deafdecacaff)
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Client (0000112e-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access (00001130-0000-1000-8000-00805f9b34fb)
UUID: Headset HS (00001131-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Bose Corporation (0000fdd2-0000-1000-8000-00805f9b34fb)
UUID: Amazon.com Services, Inc. (0000fe03-0000-1000-8000-00805f9b34fb)
UUID: Google (0000fe26-0000-1000-8000-00805f9b34fb)
UUID: Google (0000fe2c-0000-1000-8000-00805f9b34fb)
UUID: Bose Corporation (0000febe-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351)
UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15)
Modalias: bluetooth:v009Ep4020d0481
[bluetooth]#

The info I can find in the logfiles (journalctl):

Jan 14 09:58:20 laptop1 blueman-manager[3388]: blueman-manager 09.58.20 WARNING
ManagerDeviceMenu:145 fail : fail g-dbus-error-quark:
GDBus.Error:org.freedesktop.DBus.Error.Failed: blueman.bluez.errors.DB>
Jan 14 09:58:20 laptop1 blueman-manager[3388]: (0)

I can get the device connecting again using the following procedure:

Remove the device:

[bluetooth]# remove 60:AB:D2:43:BB:9C
[bluetooth]# [DEL] Device 60:AB:D2:43:BB:9C Bose QC35 II
[bluetooth]# Device has been removed

Scan for devices:

[bluetooth]# scan bredr
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller 28:16:AD:16:D9:FF Discovering: yes
[bluetooth]# [NEW] Device 60:AB:D2:43:BB:9C Bose QC35 II
[bluetooth]# [CHG] Device 60:AB:D2:43:BB:9C RSSI: 0xffffffd7 (-41)
scan off
[bluetooth]# Discovery stopped

Pair and trust device:

[bluetooth]# pair 60:AB:D2:43:BB:9C
Attempting to pair with 60:AB:D2:43:BB:9C
[CHG] Device 60:AB:D2:43:BB:9C Connected: yes
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C Bonded: yes
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs: 00000000-deca-fade-deca-
deafdecacaff
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001101-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001108-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110a-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110b-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110c-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110d-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110e-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110f-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000111e-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000112e-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001130-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001131-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001200-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
81c2e72a-0591-443e-a1ff-05f988593351
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
931c7e8a-540f-4686-b798-e8df0a2ad9f7
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
f8d1fbe4-7966-4334-8024-ff96c9330e15
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C ServicesResolved: yes
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C Paired: yes
[Bose QC35 II]# Pairing successful
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C ServicesResolved: no
[CHG] Device 60:AB:D2:43:BB:9C Connected: no
[bluet60:AB:D2:43:BB:9CB:D2:43:BB:9C
[bluetooth]# [CHG] Device 60:AB:D2:43:BB:9C Trusted: yes
[bluetooth]# Changing 60:AB:D2:43:BB:9C trust succeeded

and finally connect to the device:

[bluetooth]# connect 60:AB:D2:43:BB:9C
Attempting to connect to 60:AB:D2:43:BB:9C
[CHG] Device 60:AB:D2:43:BB:9C Connected: yes
[Bose QC35 II]# [NEW] Endpoint /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep3
[Bose QC35 II]# [NEW] Endpoint /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep51
[Bose QC35 II]# [NEW] Endpoint /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep19
[Bose QC35 II]# [NEW] Endpoint /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep49
[Bose QC35 II]# [NEW] Endpoint /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep17
[Bose QC35 II]# [NEW] Endpoint /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep33
[Bose QC35 II]# [NEW] Endpoint /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep1
[Bose QC35 II]# [NEW] Transport /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep1/fd0
[Bose QC35 II]# [CHG] Transport /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep1/fd0
Delay: 0x05dc (1500)
[Bose QC35 II]# Connection successful
[Bose QC35 II]# [NEW] Player /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/player0
[default]
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs: 00000000-deca-fade-deca-
deafdecacaff
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001101-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001108-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110a-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110b-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110c-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110d-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110e-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000110f-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000111e-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000112e-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
0000112f-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001130-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001131-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
00001200-0000-1000-8000-00805f9b34fb
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
81c2e72a-0591-443e-a1ff-05f988593351
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
931c7e8a-540f-4686-b798-e8df0a2ad9f7
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C UUIDs:
f8d1fbe4-7966-4334-8024-ff96c9330e15
[Bose QC35 II]# [CHG] Transport /org/bluez/hci0/dev_60_AB_D2_43_BB_9C/sep1/fd0
Volume: 0x0037 (55)
[Bose QC35 II]# [CHG] Device 60:AB:D2:43:BB:9C ServicesResolved: yes
[Bose QC35 II]#



-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bluez depends on:
ii dbus [default-dbus-system-bus] 1.14.10-4
ii init-system-helpers 1.66
ii kmod 31-1
ii libasound2 1.2.10-3
ii libc6 2.37-13
ii libdbus-1-3 1.14.10-4
ii libdw1 0.190-1+b1
ii libglib2.0-0 2.78.3-1
ii libreadline8 8.2-3
ii libudev1 255.2-4
ii udev 255.2-4

bluez recommends no packages.

Versions of packages bluez suggests:
pn pulseaudio-module-bluetooth <none>

-- no debconf information

Brian Tarricone

unread,
Jan 22, 2024, 4:10:04 PM1/22/24
to
I'm running into this too, poked around a little bit, and found an issue filed on BlueZ's github repo that seems like it might be related: https://github.com/bluez/bluez/issues/686

Unclear what the proper fix is; there's some complaint on there that what they merged requires a new, unreleased kernel. But there's also a patch posted in a comment that some people claim fixes it (I have not yet tested): https://github.com/bluez/bluez/issues/686#issuecomment-1858902231

Brian Tarricone

unread,
Jan 29, 2024, 3:50:05 AM1/29/24
to
Can confirm that the patch in the comment at
https://github.com/bluez/bluez/issues/686#issuecomment-1858902231 fixes the issue for me.
0 new messages