You are not logged in.
Gnome's bluetooth functionality has been broken since I installed my system. When I click the bluetooth toggle in gnome control center, it imediately toggles back off. When I click the bluetooth option in the quick settings pannel, it appears to be loading for about 30 seconds and then switches off again.
When I run
sudo dmesg
I get the following bluetooth output, leading me to suspect that the issue is hardware-related:
[ 37.945862] Bluetooth: hci0: Waiting for firmware download to complete
[ 37.946163] Bluetooth: hci0: Firmware loaded in 1525927 usecs
[ 37.946188] Bluetooth: hci0: Waiting for device to boot
[ 37.958176] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 37.958184] Bluetooth: hci0: Device booted in 11723 usecs
[ 37.958491] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc
[ 37.961168] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 37.962170] Bluetooth: hci0: Firmware revision 0.1 build 19 week 44 2021
[ 37.964188] Bluetooth: hci0: Reading supported features failed (-16)
[ 37.964191] Bluetooth: hci0: Error reading debug features
[ 37.964193] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
The two error messages that are displayed in red in dmesg also appear after booting in tty without gdm.
I've been able to start bluetooth manually with
sudo systemctl start bluetooth.service
and then connect to my device through the gnome interface. As you can imagine, this is not the most convenient approach. I would prefer to keep the service disabled by default and start it with gnome when needed.
Does anybody have an idea how this can be fixed, or where I can go to file an appropriate bug report?
Last edited by houseofleaf (2024-03-06 21:44:42)
Offline
GNOME's bluetooth implementation is not intended to autostart the service file, it's generally expected that one is already running for the GNOME implementation to connect to it. The service needs to be running gnome-bluetooth can still rfkill/disable it from a HW perspective but you need the service active.
Last edited by V1del (2024-03-06 11:30:05)
Offline
Thanks for your reply, that makes sense. I enabled the service and it's now working as expected. I had to run
rfkill block bluetooth
to set the default behaviour on boot. I suppose the login messages are unrelated. Marking this as solved!
Last edited by houseofleaf (2024-03-06 21:48:21)
Offline