[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bluetooth speakers: pairing problem in Debian trixie (GNOME)



Hello Debianites,

I've recently updated my X1 Yoga laptop to Debian trixie from
bookworm, and currently I use the GNOME desktop environment.

In bookworm I was able to pair with some bluetooth speakers I have at
home, and could reconnect to those after a reboot of the laptop.  This
would wake the speakers from their sleep power state if necessary, and
audio from the desktop environment would begin routing to them.

After the upgrade to trixie, reconnecting to the bluetooth speakers
after a reboot or when waking the laptop from sleep fails.  After
attempting to reconnect to the speakers, the bluetooth connection
status very briefly flickers (for maybe a tenth of a second) a status
of 'connected', but then the connection drops.  The speakers
themselves do not wake from sleep.

As a workaround, I can unpair/remove the device from GNOME's bluetooth
settings panel, then put the speakers into pairing mode using their
remote control, before scanning for them on the laptop and
reconnecting -- but that is comparatively quite a lot of steps
compared to simply clicking to reconnect button from the laptop (the
previous, bookworm experience).

There is cluster of error messages that appears in the output of
'journalctl -xeu bluetooth' during the failed reconnection attempts:

Aug 22 11:47:31 localhost bluetoothd[1086]:
profiles/audio/avdtp.c:avdtp_connect_cb() connect to
7C:XX:XX:XX:XX:XX: Permission denied (13)
Aug 22 11:47:31 localhost bluetoothd[1086]:
src/service.c:btd_service_connect() a2dp-source profile connect failed
for 7C:XX:XX:XX:XX:XX: Device or resource busy
Aug 22 11:47:33 localhost bluetoothd[1086]:
profiles/audio/avdtp.c:avdtp_connect_cb() connect to
7C:XX:XX:XX:XX:XX: Too many levels of symbolic links (40)

Has anyone had similar experiences following an upgrade to trixie, or
any ideas what I can do to try to diagnose and report this as a bug?

Note: there is no pairing PIN required for the speakers.

Thanks!
James


Reply to: