Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#73343 - Bluetooth can't be enabled
Attached to Project:
Arch Linux
Opened by Eric (harpium) - Thursday, 13 January 2022, 08:52 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 20 February 2022, 19:36 GMT
Opened by Eric (harpium) - Thursday, 13 January 2022, 08:52 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 20 February 2022, 19:36 GMT
|
DetailsI'm currently on GNOME, and sometimes when I go to the Bluetooth settings the
option to enable it is grayed out, so I can't connect to any of my peripherals. 'systemctl status bluetooth' tells me that the service is active. 'bt-device -l' gives me the following error: ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) Bail out! ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) [1] 4742 abort (core dumped) bt-device -l Reloading the 'btusb' module doesn't fix the issue. The only fix is to shutdown my computer, unplug the power supply for a few seconds, and then boot. |
This task depends upon
Screenshot from 2022-01-13 00...
In case it might be interesting for debugging purposes; My Bose headset makes voice announcements when it's connecting/connected/disconnected, and based on the voice announcements I receive in/from the headset, it briefly connects, and then immediately disconnects.
They make a noise indicating that they connected, and then Bluetooth immediately stops working.
I have to forget the device first before connecting to avoid this bug.
Running `bt-device -c 04:21:44:40:97:64` produces: `Failed to start SDP discovery. Please make sure you have bluez-utils installed on your system.`
I have bluez-utils installed.
Running `bluetoothctl` and `connect 04:21:44:40:97:64` results in connection established and BT speaker works fine.
Might be related. but I get this constantly repeating error in journalctl:
```
Feb 08 20:48:09 eric-laptop bluetoothd[28506]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 08 20:48:09 eric-laptop bluetoothd[28506]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 08 20:48:09 eric-laptop bluetoothd[28506]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
```
```
$ pacman -Qs bluez | grep local/
local/bluez 5.63-2
local/bluez-libs 5.63-2
local/bluez-tools 0.2.0-5
local/bluez-utils 5.63-2
```