You are not logged in.
Hey, I'm a newbie in the forum, but, i have a problem. When I try to power on my Bluetooth adaptor, they just power off after 1ms. The only error I found is in the `bluetooth.service`, and that is the error:
Log:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Tue 2022-08-23 11:56:44 -03; 11min ago
Docs: man:bluetoothd(8)
Main PID: 492 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9444)
Memory: 2.6M
CPU: 134ms
CGroup: /system.slice/bluetooth.service
└─492 /usr/lib/bluetooth/bluetoothd
Aug 23 11:58:20 death-star bluetoothd[492]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/sbc_xq
Aug 23 11:58:20 death-star bluetoothd[492]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/sbc_xq
Aug 23 11:58:20 death-star bluetoothd[492]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Aug 23 11:58:20 death-star bluetoothd[492]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Aug 23 11:58:20 death-star bluetoothd[492]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Aug 23 11:58:20 death-star bluetoothd[492]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Aug 23 11:58:20 death-star bluetoothd[492]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/faststream
Aug 23 11:58:20 death-star bluetoothd[492]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/faststream_duplex
Aug 23 11:58:20 death-star bluetoothd[492]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
Aug 23 11:58:22 death-star bluetoothd[492]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
System info:
kernel: 5.19.3-arch1-1
bluetoothctl: 5.65
Offline
Hi, I had this issue as well but I was able to use bluetoothctl to connect to my devices manually. After doing this, I was able to restart the service and it worked fine.
Offline