Ubuntu refuses to reconnect to my bluetooth device
Table of Contents
Context
I’ve already connected my XUbuntu 22.04 (LTS) laptop plenty of times to my Ultimate Ears Boom 2 wireless speaker.
All of a sudden, this morning, my laptop refuses to connect to my speaker without any obvious reason:
My wireless speaker was still listed in my Recent Connections and I wasn’t in a new device pairing situation.
Analysis
This step was quite quick but I still wan’t to log the messages that appeared in my laptop system logs:
root@ubuntu:~# journalctl -f -n 0
Jul 20 11:50:07 ubuntu.local bluetoothd[8636]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to XX:XX:XX:XX:XX:XX: Permission denied (13)
Jul 20 11:50:07 ubuntu.local blueman-manager[8655]: blueman-manager 15.50.07 WARNING ManagerDeviceMenu:141 fail : fail g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Failed: blueman.bluez.errors.DBusFailedError: br-connection-canceled
Jul 20 11:50:07 ubuntu.local blueman-manager[8655]: (0)
Jul 20 11:50:11 ubuntu.local bluetoothd[8636]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to XX:XX:XX:XX:XX:XX: Too many levels of symbolic links (40)
Jul 20 11:50:11 ubuntu.local bluetoothd[8636]: src/service.c:btd_service_connect() a2dp-source profile connect failed for XX:XX:XX:XX:XX:XX: Device or resource busy
Jul 20 11:50:17 ubuntu.local bluetoothd[8636]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to XX:XX:XX:XX:XX:XX: Permission denied (13)
Here were my system details when the problem occurs:
❯ dpkg -la |grep -i blue | sort -k2
ii blueman 2.2.4-1 amd64 Graphical bluetooth manager
ii bluez 5.64-0ubuntu1 amd64 Bluetooth tools and daemons
ii bluez-cups 5.64-0ubuntu1 amd64 Bluetooth printer driver for CUPS
ii bluez-obexd 5.64-0ubuntu1 amd64 bluez obex daemon
ii libbluetooth3:amd64 5.64-0ubuntu1 amd64 Library to use the BlueZ Linux Bluetooth stack
ii pulseaudio-module-bluetooth 1:15.99.1+dfsg1-1ubuntu1 amd64 Bluetooth module for PulseAudio sound server
Quick and dirty solution
I didn’t spent too much time looking for the root cause of this problem.
My quick and dirty solution was to remove the device from the known device list using the U.I:
and then create a new pairing with my bluetooth speaker:
That’s it. Still not sure what went wrong here. Nevermind, my bluetooth speaker is now working as before and I’m ready to rock !
Be the first to leave a comment! 🥇