Arch Linux

JKing

Member

Registered: 2023-08-08

Posts: 7

Bluetooth suddenly stopped working

When I booted my computer this morning, Bluetooth devices were not working, despite my not changing any configuration and no recent updates to Bluez occurring.`rfkill list` did show me that the hci0 device was soft-blocked, so I unblocked it, but to no avail. I tried removing Bluez, deleting configuration, and re-installing, also to no avail. `journalctl` shows nothing amiss. If I remove a device, I cannot pair it: nothing shows up in a scan. Can anyone suggest some diagnostic steps?

Output of journalctl:

[jking@arachne ~]$ journalctl -b -u bluetooth
Oct 20 10:30:59 arachne systemd[1]: Starting Bluetooth service...
Oct 20 10:31:00 arachne bluetoothd[2084]: Bluetooth daemon 5.78
Oct 20 10:31:00 arachne systemd[1]: Started Bluetooth service.
Oct 20 10:31:00 arachne bluetoothd[2084]: Starting SDP server
Oct 20 10:31:00 arachne bluetoothd[2084]: src/plugin.c:init_plugin() System does not support bap plugin
Oct 20 10:31:00 arachne bluetoothd[2084]: src/plugin.c:init_plugin() System does not support bass plugin
Oct 20 10:31:00 arachne bluetoothd[2084]: src/plugin.c:init_plugin() System does not support mcp plugin
Oct 20 10:31:00 arachne bluetoothd[2084]: src/plugin.c:init_plugin() System does not support vcp plugin
Oct 20 10:31:00 arachne bluetoothd[2084]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Oct 20 10:31:00 arachne bluetoothd[2084]: src/plugin.c:init_plugin() System does not support micp plugin
Oct 20 10:31:00 arachne bluetoothd[2084]: src/plugin.c:init_plugin() System does not support ccp plugin
Oct 20 10:31:00 arachne bluetoothd[2084]: src/plugin.c:init_plugin() System does not support csip plugin
Oct 20 10:31:00 arachne bluetoothd[2084]: src/plugin.c:init_plugin() System does not support asha plugin
Oct 20 10:31:00 arachne bluetoothd[2084]: Bluetooth management interface 1.23 initialized
Oct 20 10:31:00 arachne bluetoothd[2084]: Battery Provider Manager created
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/ldac
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/aptx_hd
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx_hd
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/aptx
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/aac
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aac
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/opus_g
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/opus_g
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/faststream
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/faststream_duplex
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/opus_05
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/opus_05
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Oct 20 10:31:00 arachne bluetoothd[2084]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Oct 20 10:31:46 arachne bluetoothd[2084]: Controller resume with wake event 0x0

Output of lsusb:

[jking@arachne ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 3434:02a0 Keychron Keychron K10 Pro
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 1038:12b3 SteelSeries ApS SteelSeries Arctis 1 Wireless
Bus 001 Device 006: ID 1462:7c90 Micro Star International MYSTIC LIGHT 
Bus 001 Device 007: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Output of bluetoothctl:

[jking@arachne ~]$ bluetoothctl
hci0 new_settings: powered bondable ssp br/edr le secure-conn wide-band-speech 
[bluetooth]# Agent registered
[bluetooth]# [CHG] Controller 98:43:FA:58:0E:CF Pairable: yes
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# scan off
[bluetooth]# Failed to stop discovery: org.bluez.Error.Failed
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Failed to start discovery: org.bluez.Error.InProgress

Installed packages:

[jking@arachne ~]$ pacman -Qs bluez
local/bluez 5.78-1
    Daemons for the bluetooth protocol stack
local/bluez-libs 5.78-1
    Deprecated libraries for the bluetooth protocol stack
local/bluez-utils 5.78-1
    Development and debugging utilities for the bluetooth protocol stack

kermit63

Member

Registered: 2018-07-04

Posts: 370

Re: Bluetooth suddenly stopped working

check your pacman logs if your bluetooth problems coincide with kernel updates.

I'm no expert at diagnosing bluetooth failures, but in my experience, bluetooth devices are very susceptible to kernel updates. At least in my case, whenever I encounter bluetooth problems, I just downgrade to the previous kernel, or boot into the LTS kernel, and the problems go away. Then I include the problematic kernel in the IgnorePkg list in /etc/pacman.conf, until a newer kernel comes in.

---

Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.

JKing

Member

Registered: 2023-08-08

Posts: 7

Re: Bluetooth suddenly stopped working

check your pacman logs if your bluetooth problems coincide with kernel updates.

I'm no expert at diagnosing bluetooth failures, but in my experience, bluetooth devices are very susceptible to kernel updates. At least in my case, whenever I encounter bluetooth problems, I just downgrade to the previous kernel, or boot into the LTS kernel, and the problems go away. Then I include the problematic kernel in the IgnorePkg list in /etc/pacman.conf, until a newer kernel comes in.

That was good advice. Thank you. I had indeed applied a kernel update last night and forgot, so downgrading from 6.11.4 to 6.11.3 restored functionality.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,634

Re: Bluetooth suddenly stopped working

Intel Bluetooth / WiFi?

Perhaps https://bbs.archlinux.org/viewtopic.php?id=300382  ?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way