The Bluetooth service is running, but not working

Information:
Operating System: EndeavourOS
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.4.1-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3317U CPU @ 1.70GHz
Memory: 11.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: S500CA
System Version: 1.0

I’ve just started using this approachable OS last week, but I had a problem today
Now It’s midnight on my loclation.
My Bluetooth works perfectly before this evening
But now my Bluetooth doesn’t work after disconnecting,
I’m not sure if it’s related, At night I installed the “Barrier” to share my mouse and keyboard.
After that I wanted to switch back to a separate keyboard bluetooth connection and then the problem happened.

Now I can start the service and the status doesn’t seem to be wrong

[benny@benny500ca ~]$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sun 2023-07-02 23:44:22 CST; 42s ago
       Docs: man:bluetoothd(8)
   Main PID: 517 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 14188)
     Memory: 2.7M
        CPU: 87ms
     CGroup: /system.slice/bluetooth.service
             └─517 /usr/lib/bluetooth/bluetoothd

 7月 02 23:44:22 benny-s500ca systemd[1]: Starting Bluetooth service...
 7月 02 23:44:22 benny-s500ca bluetoothd[517]: Bluetooth daemon 5.68
 7月 02 23:44:22 benny-s500ca systemd[1]: Started Bluetooth service.
 7月 02 23:44:22 benny-s500ca bluetoothd[517]: Starting SDP server
 7月 02 23:44:22 benny-s500ca bluetoothd[517]: Bluetooth management interface 1.22 initialized

But the KDE blueooth setting page just show a message “bluetooth is not runing” and a enable button.Also I can not find or connect any bluetooth device.
Really need some help to resume my bluetooth…

update some try

[benny@benny500ca ~]$ sudo bluetoothctl
Agent registered
[bluetooth]# scan on
No default controller available

Welcome to the forum benny! :octopus:

Please try running rfkill and see if bluetooth is blocked or straight up run rfkill unblock bluetooth. Whenever I get that message in bluetoothctl, that’s what’s up

[benny@benny500ca ~]$ rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked

Here is the resault

bluetoothctl power on

Also, see:

:v:

not work for me

bluetoothctl power on
No default controller available
bluetoothctl scan on
No default controller available

You could check the output of this…

inxi -Fxxc0z

…only watching the messages under NETWORK and BLUETOOTH.

It may be an issue of a chipset, that carries both functionalities (WiFi and BT) in one chip. Those chipsets often are very unreliable and buggy, and in many cases not supporting Linux (but have problems on Windows, as well).

From running that command, can you tell us the BT chip (and driver in use) on your computer?

And, oh yes, welcome to the forum! :enos:

@benny3273

You can just post inxi -Na which will give the network hardware.

Thank you all for your help.
After waking up the next day and open system, the bluetooth is working well as before.

I still don’t know How and Why, I reboot machine many times yesterday and it still hasn’t recovered, but today it worked.

Here is what the command “inxi -Na” show me

Network:
  Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: AzureWave
    driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 168c:0032 class-ID: 0280
  Device-2: Qualcomm Atheros AR8161 Gigabit Ethernet vendor: ASUSTeK
    driver: alx v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 03:00.0 chip-ID: 1969:1091 class-ID: 0200

Well there were a number of updates that included firmware. But it could have also been something else or another update? Glad it’s working for you.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.