Bluetooth not working anymore

After recent update (I think the big one with the new Plasma), my bluetooth isnt working. I am unable to enable it in the Plasma GUI settings, when I click on the enable button, nothing happens. I found some errors on systemctl bluetooth status, which may lead to a solution, but I do not know how to address them. I hope someone can help. Please be kind; I only know enough linux to get myself in trouble.

Here is some inxi info:

System:
Kernel: 6.2.10-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-6.2-x86_64
root=UUID=a4677c34-08ee-4217-a8f8-04d583d29686 ro quiet apparmor=1
security=apparmor resume=UUID=54b33f09-d1e4-45c1-85ed-60965f977595
udev.log_priority=3
Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial:
Mobo: ASUSTeK model: TUF GAMING X570-PRO (WI-FI) v: Rev X.0x
serial: UEFI: American Megatrends v: 4021
date: 08/10/2021
CPU:
Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.2.10-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 0.3.68 status: off with: pipewire-media-session
status: active tools: pw-cli
Server-3: PulseAudio v: 16.1 status: active with: pulseaudio-jack
type: module tools: pacat,pactl,pavucontrol
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:2
chip-ID: 8087:0029 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: N/A

here is the bluetooth status info with the errors:

systemctl status bluetooth  :heavy_check_mark:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Tue 2023-04-11 10:20:18 MDT; 5min ago
Docs: man:bluetoothd(8)
Main PID: 798 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 38398)
Memory: 2.2M
CPU: 14ms
CGroup: /system.slice/bluetooth.service
└─798 /usr/lib/bluetooth/bluetoothd

Apr 11 10:20:16 patience bluetoothd[798]: Bluetooth daemon 5.66
Apr 11 10:20:18 patience systemd[1]: Started Bluetooth service.
Apr 11 10:20:18 patience bluetoothd[798]: Starting SDP server
Apr 11 10:20:18 patience bluetoothd[798]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Apr 11 10:20:18 patience bluetoothd[798]: src/plugin.c:plugin_init() Failed to init vcp plugin
Apr 11 10:20:18 patience bluetoothd[798]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Apr 11 10:20:18 patience bluetoothd[798]: src/plugin.c:plugin_init() Failed to init mcp plugin
Apr 11 10:20:18 patience bluetoothd[798]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Apr 11 10:20:18 patience bluetoothd[798]: src/plugin.c:plugin_init() Failed to init bap plugin
Apr 11 10:20:18 patience bluetoothd[798]: Bluetooth management interface 1.22 initialized

Obviously I need to change the preset to enabled but i dont know how. Also I dont know where to find or how to enable those plugins. Any help would be greatly appreciated!

Edit: Here are some screenshots that might help explain the situation:
image
(Clicking the enable button does nothing)


(system settings gui shows bluetooth running)

rfkill output:
hci0: Bluetooth
Soft blocked: no
Hard blocked: no

No
preset is only enabled if you set the service up as user e.g.

sudo systemctl enable --now --user bluetooth
Most services are set up without --user.

Thanks for the quick reply! Do you mean that The preset setting is unrelated to my ability to use bluetooth, or that I should apply that command??

I think the former.

1 Like

Any ideas about what might help?

I found my own solution-- if you have a similar problem, try turning off bluetooth in your system bios, rebooting, the turning bluetooth back on in the BIOS. That solved it for me.

1 Like

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