The bluetooth no longer works. The icon appears in Gnome but when I turn on the switch in settings it automatically turns off.
systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Fri 2023-11-24 17:02:04 CET; 2min 5s ago
Docs: man:bluetoothd(8)
Main PID: 1089 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 19007)
Memory: 2.1M
CPU: 37ms
CGroup: /system.slice/bluetooth.service
└─1089 /usr/libexec/bluetooth/bluetoothd
nov. 24 17:02:03 fedora bluetoothd[1089]: Starting SDP server
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support csip plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support micp plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support vcp plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support mcp plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support bass plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support bap plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: Bluetooth management interface 1.22 initialized
nov. 24 17:02:04 fedora systemd[1]: Started bluetooth.service - Bluetooth service.
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 001 Device 003: ID 0b05:1939 ASUSTek Computer, Inc. [unknown]
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 2516:0051 Cooler Master Co., Ltd. [unknown]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
Bus 003 Device 003: ID 04d9:a1cd Holtek Semiconductor, Inc. [unknown]
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
This seems to indicate that bluetooth is an intel chipset, and may be the same as mine.
You may be able to see more info on that particular device with lspci -nnk and selecting the info for the wifi network device.
Then add the output of lsusb -v -s 001:002 to show the detailed portion for that particular bluetooth device.
In my experience usually intel packages the wifi and bluetooth devices together so the combination of devices show on the different listings even though they are a single chipset
I have encountered problems with Bluetooth as well, however the first device I connected, a pair of Treblab XR200 earbuds seem to work just fine. I paired 3 other headphones, which connected and then disconnected with a few seconds. The internal bluetooth is Intel, but I got the same behaviour with an Asus bluetooth dongle.
lsusb gives, in part:
Bus 001 Device 006: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 007: ID 0b05:17cb ASUSTek Computer, Inc. Broadcom BCM20702A0 Bluetooth
This is a fresh install of Fedora 39 Cinnamon on a Dell Latitude 5590.
Just updated and rebooted, no change in operation.
I seem to be having the same issue. I came back from several days away to find that my bluetooth keyboard/mouse combo no longer worked. I figured the problem would solve itself after update/restart but nada.
I also have an Intel Ax200 network controller. When I run
My systemctl status bluetooth output looks similar to yours
[20:44:37]$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Tue 2023-12-26 20:27:56 EST; 16min ago
Docs: man:bluetoothd(8)
Main PID: 10848 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 38361)
Memory: 600.0K
CPU: 32ms
CGroup: /system.slice/bluetooth.service
└─10848 /usr/libexec/bluetooth/bluetoothd
Dec 26 20:27:56 drcomputer systemd[1]: Started bluetooth.service - Bluetooth service.
Dec 26 20:27:56 drcomputer bluetoothd[10848]: Starting SDP server
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support csip plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support micp plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support vcp plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support mcp plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support bass plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support bap plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: Bluetooth management interface 1.22 initialized
Similar story here – came back to the computer after the holidays and found my bluetooth audio not working. My mouse (thankfully) is working great.
Jan 03 11:29:19 afterman bluetoothd[1439440]: Bluetooth daemon 5.71
Jan 03 11:29:19 afterman bluetoothd[1439440]: Starting SDP server
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support csip plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support micp plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support vcp plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support mcp plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support bass plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support bap plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: Bluetooth management interface 1.22 initialized
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Battery Provider Manager created
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Jan 03 11:29:19 afterman bluetoothd[1439440]: Failed to clear UUIDs: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Failed to add UUID: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Failed to add UUID: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Failed to add UUID: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Player registered: sender=:1.49 path=/_1_294
Jan 03 11:29:19 afterman bluetoothd[1439440]: Player registered: sender=:1.49 path=/_1_16676
Jan 03 11:29:19 afterman bluetoothd[1439440]: Player registered: sender=:1.49 path=/_1_133
Jan 03 11:29:20 afterman bluetoothd[1439440]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Jan 03 11:29:20 afterman bluetoothd[1439440]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/ldac
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/aptx
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/aac
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aac
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/sbc
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/sbc
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/sbc_xq
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/sbc_xq
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/faststream
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/opus_05
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/opus_05
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Connecting my Sony WH-1000XM4s gives:
Jan 03 11:37:46 afterman bluetoothd[1439440]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 14:3F:A6:09:5F:0C: Protocol not available
What kernel are you running? I have found kernel 6.7.7 to be more stable for Bluetooth.
You can try bluetoothctl devices Check if your device is in the list. We can try :
Pairing the Device: If your device is not listed, try putting the mouse in pairing mode. Refer to the mouse manual for instructions. Then, run: bluetoothctl then Within the Bluetooth CLI, enter the following commands:
power on
agent on
default-agent
scan on
After scanning, you should see your mouse in the list. Pair with it using: pair XX:XX:XX:XX:XX:XX
Same problems after updating kernel twice in a row (Fedora 39). It seems every other kernel update kills bluetooth on Fedora. Can someone please check bluetooth on this chipset in the future? My fix is to reboot to two kernels back every time I restart. I’m on KDE, not Gnome, but the same behavior even on a terminal with the dreaded:
bluetoothctl show
No default controller available
…yet, I still get the “Intel Corp. AX200 Bluetooth” showing up on “lsusb”. Multiple devices with same chipset for bluetooth.
Currently running kernel 6.7.10-200.fc39.x86_64 (working on F39 with bluetooth)