Can't Enable Bluetooth Fedora Silverblue 41

Ask Fedora
, , , , ,
1

I’m fairly new to Fedora Silverblue, I’ve been using it since December or so for pretty much everything, I dual boot this and Windows. Bluetooth was fine initially, but stopped working around Feburary 17th, and I looked at previous posts before but couldn’t solve my issue. I click the switch but it doesn’t turn on, and I know it’s not the device because it works fine on my Windows partition.

Here’s what I’ve gotten so far:

  • Fedora Linux 41.20250317.0 (Silverblue)
  • Kernel - Linux 6.13.6-200.fc41.x86_64

Everything below is using commands I found in other posts:

Hardware

$ inxi --bluetooth
Bluetooth:
  Device-1: Lite-On Wireless_Device driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: N/A

Wireless Radios

$ bluetoothctl
[bluetooth]# Agent registered
[bluetooth]# power on
No default controller available
[bluetooth]# 

$ journalctl -b | grep Bluetooth
Mar 17 17:22:53 fedora kernel: Bluetooth: Core ver 2.22
Mar 17 17:22:53 fedora kernel: Bluetooth: HCI device and connection manager initialized
Mar 17 17:22:53 fedora kernel: Bluetooth: HCI socket layer initialized
Mar 17 17:22:53 fedora kernel: Bluetooth: L2CAP socket layer initialized
Mar 17 17:22:53 fedora kernel: Bluetooth: SCO socket layer initialized
Mar 17 17:22:55 fedora systemd[1]: Starting bluetooth.service - Bluetooth service...
Mar 17 17:22:55 fedora bluetoothd[1052]: Bluetooth daemon 5.79
Mar 17 17:22:55 fedora systemd[1]: Started bluetooth.service - Bluetooth service.
Mar 17 17:22:55 fedora systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Mar 17 17:22:55 fedora kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Mar 17 17:22:55 fedora kernel: Bluetooth: BNEP filters: protocol multicast
Mar 17 17:22:55 fedora kernel: Bluetooth: BNEP socket layer initialized
Mar 17 17:22:55 fedora bluetoothd[1052]: Bluetooth management interface 1.23 initialized
Mar 17 17:22:56 fedora systemd[1312]: Started mpris-proxy.service - Bluetooth mpris proxy.
Mar 17 17:23:41 fedora systemd[2088]: Started mpris-proxy.service - Bluetooth mpris proxy.
Mar 17 17:23:55 fedora systemd[1312]: Stopping mpris-proxy.service - Bluetooth mpris proxy...
Mar 17 17:23:55 fedora systemd[1312]: Stopped mpris-proxy.service - Bluetooth mpris proxy.

$ rfkill list all
0: acer-wireless: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: acer-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

I’ve seen some posts saying Kernel 13 might have issues with Bluetooth, so how would I go about changing kernels? I’m not exactly sure on what version to change to to avoid any other hardware problems, and I’m not sure about making backups…

2

On atomic desktops it would be easier to roll back to an older commit, and pin that deployment. I expect a 4-week old commit would still contain a 6.12.xx kernel.

However, that would keep all the packages from the base system on an older version, which certainly has drawbacks.

1 Like
3

Okay, I knew Silverblue could do rollbacks, I picked it for the purpose of not worrying about breaking stuff. Unfortunate that I have to stay on older versions until the bug is fixed. Thank you!

Edit: I rolled back to a January commit because even some of the older Feburary commits around the 10th didn’t work, and it seems kernel 6.12.11 and up didn’t want to work, so I stuck with 6.12.10. For future reference, is there an easier way to see kernel changes by commit? I did rpm-sotree db list [commit] | grep kernel and rpm-ostree db diff but it was a little tiring checking each commit for kernel info…

4

I don’t think there’s any rpm-ostree subcommand that would present change logs for a specific package in different commits.

However, given that the server-side commits are being built based on the specific RPM packages available at build-time in the corresponding repositories, you can always track the changes in Bodhi, e.g. for kernels in F41:
https://bodhi.fedoraproject.org/updates/?search=&packages=kernel&releases=F41

Alternatively, you can run the dnf changelog command in a Toolbx container:

dnf changelog --count=5 kernel