Fed 33 Settings / Bluetooth won't activate

Recently in the Settings / Bluetooth, When switched to ON will not change the status, it does not activate the Blooth radio.
I have a dual boot w / Windows 10 and there the BT works. So the radio sender must / should be okay. I have done a rfkill list and it shows: 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
And as far as I know all other indications say BT is active.
I have read that someone else had the same problem, changed the OS and the BT worked.
So he reported it as a Fedora 33 bug.
What is the actual status and / or will there be a fix, or is there some work around?
I have followed many online suggestions and sudo this and sudo that but to no avail.
All indications say the Bluetooth is active. In the settings it just don’t change from “off” to “on”.
Thanks for any feed back / tips / suggestions…

1 Like

I have exactly this problem. Following an update bluetooth is off and toggling it back on in settings makes no difference. My keyboard no longer works which is kinda hard. Im using 33 on a 2010 imac. Any suggestions or advice?

This isn’t much of an expanation, but mine is working now… I would try disabling the service, open a terminal and
systemctl disable bluetooth.service to prevent it starting up on system boot
reboot the system and manually start the service
systemctl start bluetooth.service

journal still shows some warnings, but I can remove devices and re-connect…

thanks for the suggestion but when i run either command i start getting hundreds of paragraph returns (i think) in the terminal or wharever window i place the focus on and this continues for a couple of minutes. no idea whats happening. the command dont seem to have the desired effect

bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2021-02-22 13:54:02 AEDT; 20min ago
Docs: man:bluetoothd(8)
Main PID: 6139 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 9480)
Memory: 1.6M
CPU: 48ms
CGroup: /system.slice/bluetooth.service
└─6139 /usr/libexec/bluetooth/bluetoothd

Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalConnect” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowConnect” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEMinConnectionInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEMaxConnectionInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionLatency” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTimeout” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in group “Controller”
Feb 22 13:54:02 ikymaki systemd[1]: Started Bluetooth service.
Feb 22 13:54:02 ikymaki bluetoothd[6139]: Starting SDP server
Feb 22 13:54:02 ikymaki bluetoothd[6139]: Bluetooth management interface 1.18 initialized

I managed to find a log, but it does not mean muchto me, I dont understand the cause of the errors.

Feb 22 13:54:02 ikymaki bluetoothd[6139]: Bluetooth management interface 1.18 initialized
Feb 22 13:54:02 ikymaki bluetoothd[6139]: Starting SDP server
Feb 22 13:54:02 ikymaki systemd[1]: Started Bluetooth service.
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTimeout” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionLatency” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEMaxConnectionInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEMinConnectionInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowConnect” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalConnect” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowAdvMonitor” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalAdvMonitor” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowDiscovery” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalDiscovery” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowSuspend” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalSuspend” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowAutoConnect” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalAutoConnect” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEMultiAdvertisementRotationInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEMaxAdvertisementInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “LEMinAdvertisementInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRMaxSniffInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRMinSniffInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRPageTimeout” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRLinkSupervisionTimeout” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRInquiryScanWindow” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRInquiryScanInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRInquiryScanType” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRPageScanWindow” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRPageScanInterval” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: src/main.c:parse_controller_config() Key file does not have key “BRPageScanType” in group “Controller”
Feb 22 13:54:02 ikymaki bluetoothd[6139]: Bluetooth daemon 5.55
Feb 22 13:54:02 ikymaki systemd[1]: Starting Bluetooth service…

It’s been a while since I last visited this problem - so sorry if I’m a bit vague…
Try having a look at what bluetooth related units are installed:
systemctl list-unit-files | grep blue
Turn everything off and re-enable one at a time…

Try removing any known devices as well… btw when I check my journal:
journalctl -eu bluetooth -e end of journal -u to filter for a unit
I still get the same parse_controller config() warnings but I can manually start bluetooth

If you are able, try an earlier kernel version, I know this resolved a few issues for me. For example, I had 2.5GB ethernet nic on my motherboard that didn’t work at first but got resolved in later kernels. I just reverted back for a while…

Thanks, all I get is:

[nathan@ikymaki ~]$ systemctl list-unit-files | grep blue
bluetooth.service disabled enabled
bluetooth.target static -

im not sure how to turn things off an on.
I will get my hands on a wired keyboard today an see if i can use a different kernel

i tried restarting bluetooth and got the following response. Does anyone know if this is significant?

[nathan@ikymaki ~]$ /bin/systemctl restart bluetooth.service
Failed to add a watch for /run/systemd/ask-password: inotify watch limit reached

Okay, so having run the command and received this response my bluetooth is now working! Still if anyone knows if the above response has any significance then I’d still be interested in knowing to preven future problems.

After installing Fedora34 about a month ago, the bluetooth was working with the new version.
Am happy again. !

In my case, the problem persists after upgrading to Fedora 34. When I do a rfkill list, it shows my bluetooth as soft blocked. It works again after doing a systemctl restart bluetooth.service, but I’d have to do that everytime I want to use bluetooth.

I also experience another problem which I think may be related to the physical bluetooth controller on the motherboard. I sometimes have the situation where bluetooth won’t turn on and/or stay on…
I have been able to resolve it by:

  1. shutting down my pc
  2. switch of power at the power supply unit
  3. unplug the power supply unit from the back of the pc
  4. wait about 1 minute for power to dissapate from system
  5. plug in power supply unit to back of pc
  6. switch on power supply unit
  7. turn on and bluetooth is working again!
    go figure…

btw… I’ve got a B550 Aorous Pro WiFi motherboard

Hello all, with my system Fed34 ASUS N75 series, the Bluetooth is actually on by a fresh start up. It is indicated in the Dropdown upper right corner and in Settings.
But once turned off, won’t turn on again, either by the dropdown or settings. It asks to “turn on” but when clicked to turn on, it doesn’t. Also in "settings, the flipper goes to blue but the text doesn’t not say BT on.
It needs another, shut down. Restart also won’t turn it on. It has to be a complete shutdown, but without disconnecting the power supply.
It must be something in the software, as BT works on the same PC (dual boot) with Windows 10.
Does anyone know it the IT people know about this?

That type of issue should be reported as a bug so the developers have a chance to know about it and find the solution.
bugzilla.redhat.com