So a new issue that started recently, I enable my Bluetooth, but when I go into settings it shows it's not enabled and when I click add device from the tray it says "Your Bluetooth adapter is not pairable". Not sure what's going on. I've tried manually installing the driver, but no luck. Running on Plasma shannon, fully updated. Bluetooth/WiFi adapter is an Intel AX200. Here is the output of commands I've tried so far.

`bruce@s145-15api ~ $ modprobe btusb
bruce@s145-15api ~ $ sudo systemctl enable bluetooth.service
Password:
bruce@s145-15api ~ $ sudo systemctl start bluetooth.service
bruce@s145-15api ~ $ systemctl is-enabled bluetooth
enabled
bruce@s145-15api ~ $ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-06-06 11:18:38 EDT; 6min ago
Docs: man:bluetoothd(8)
Main PID: 698 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 11730)
Memory: 1.9M
CPU: 30ms
CGroup: /system.slice/bluetooth.service
└─698 /usr/lib64/bluez/bluetooth/bluetoothd

Warning: some journal files were not opened due to insufficient permissions.
bruce@s145-15api ~ $ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-06-06 11:18:38 EDT; 6min ago
Docs: man:bluetoothd(8)
Main PID: 698 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 11730)
Memory: 1.9M
CPU: 30ms
CGroup: /system.slice/bluetooth.service
└─698 /usr/lib64/bluez/bluetooth/bluetoothd

Jun 06 11:18:38 s145-15api systemd[1]: Starting Bluetooth service...
Jun 06 11:18:38 s145-15api bluetoothd[698]: Bluetooth daemon 5.58
Jun 06 11:18:38 s145-15api systemd[1]: Started Bluetooth service.
Jun 06 11:18:38 s145-15api bluetoothd[698]: Starting SDP server
Jun 06 11:18:38 s145-15api bluetoothd[698]: Bluetooth management interface 1.19 initialized
Jun 06 11:18:38 s145-15api bluetoothd[698]: Failed to set mode: Blocked through rfkill (0x12)
Jun 06 11:18:46 s145-15api bluetoothd[698]: Endpoint registered: sender=:1.39 path=/MediaEndpoint/A2DPSink/>
Jun 06 11:18:46 s145-15api bluetoothd[698]: Endpoint registered: sender=:1.39 path=/MediaEndpoint/A2DPSourc>

bruce@s145-15api ~ $ rfkill
ID TYPE DEVICE SOFT HARD
0 wlan ideapad_wlan unblocked unblocked
1 bluetooth ideapad_bluetooth unblocked unblocked
2 bluetooth hci0 unblocked unblocked
3 wlan phy0 unblocked unblocked
bruce@s145-15api ~ $ blutoothctl
bash: blutoothctl: command not found
bruce@s145-15api ~ $ bluetoothctl
Agent registered
[bluetooth]# show
Controller A4:B1:C1:36:53:11 (public)
Name: s145-15api
Alias: s145-15api
Class: 0x00000000
Powered: no
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d053A
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x06 (6)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
[bluetooth]# agent KeyboardOnly
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Busy
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady`

Any help is greatly appreciated.

    Brucehankins Your Bluetooth adapter is not pairable

    That seems like a pretty clear description of the problem. Question is, why? Is it a USB dongle, or part of the motherboard? (I'm not familiar with an AX200.)

        WetGeek it's an m.2 adapter on the mobo. Does WiFi-6 and Bluetooth. It's a pretty common model, and was working fine until recently.

          Girtablulu I tried sudo eopkg install --reinstall bluez bluez-qt bluedevil but no change. Can't power it on or enable from CLI or GUI.

              Girtablulu That worked perfectly. Bluetooth works as it should. So I'll have to reinstall the older version until the new version of Bluez is fixed upstream?

                  Brucehankins would be handy if you could a bug report upstream as well I haven't found anything but if you up for a test I rebuild blue-qt and bluedevil against the new version, wanna check if this is fixing it?


                      Girtablulu I'll test it out, what do you need me to do? I'll also report the issue upstream as well.

                      Contact info is in my bio if want to reach out off the forums.

                          Brucehankins update bluez to the latest versoin and install the 2 packages above and check if the rebuilds fix anything. if not reinstall bluez-qt and b luedevil from the repo, install the old bluez again

                              Girtablulu did not fix the issue. Can not enable Bluetooth still with the updated packages.

                              I did try enabling it through the System Settings app, and through the CLI again also.

                                12 days later

                                @Brucehankins I think your issue is this one (that issue mentions gnome-settings but KDE most likely uses the same interface that gnome-settings uses to interact with bluetoothd). We just updated bluez with the patch for that issue so this should be resolved after the next unstable to stable sync.