Bluetooth is EXTREMELY bugged out in F42 KDE (also in F41 KDE!)

STILL NOT FIXED WITH KERNEL UPDATE 6.15.9-201.fc42.x86_64 (64-bit)

I also tried out the latest builds of OpenSUSE Tumbleweed & a prior build (kernel 6.15.8) on the live ISOs and NO ISSUES.

So it’s probably a fedora thing and not a Linux Kernel thing? If this don’t get fixed I’d probably have to look at something else… I don’t want to do that because I love fedora, everything else about it is just great. If this bluetooth thing doesn’t get fixed probably it’s not for me then.

It’s unfortunate that you’ve already tried various solutions but the Bluetooth problem persists.

If I were you, I would test it without changing any settings and without entering any audio stack-related commands. Try connecting the Bluetooth device to a newly installed system (using Fedora Live ISO) and see if the connection dropout problem occurs again.

If the problem persists even after a fresh installation, it is more likely to be a hardware or kernel bug rather than a software configuration issue.

This has happened to me twice. I suspected compatibility issues with the Bluetooth device and the kernel, but it worked on both newly installed systems (two different distros).

Of course, your case may be different, but I’m letting you know in case you’re interested.

The problem is, I don’t want to do a fresh install on the problematic hardware, because I fear it might mess up my GRUB. I have Btrfs snapshots set up with grub-btrfs, and everything is working smoothly. Why tinker with it if there’s a chance something could go wrong.
I tried to get a fresh Fedora 42 ISO from fedoraproject.org to test out my bluetooth in the live environment, but it seems the ISO hasn’t been updated since the release.
Mind if I ask, is there a place to ask the fedora people to request an upload of a newer ISO of fedora 42?

The official ISOs are not updated after the release date, but you can download a ā€œrespinā€ ISO which includes post-release updates.

2 Likes

Thanks for that…

Yeah, no, this is 100% a Fedora issue. I tried out the Fedora Respin live ISO from 1st August 2025, with kernel 6.15.8-200.fc42.x86_64 (64-bit) and the same issue occurs. It can’t be my hardware since: Using Ventoy I tried out debian 13 and openSUSE Tumbleweed 5 Aug 2025 and bluetooth works fine in BOTH. Also, as I cited before:

If it’s not fixed with kernel 6.16, I’m moving to debian. As I’m a student, I desperately need bluetooth, unfortunately.
I’d like to reiterate that ā€œsudo systemctl restart bluetoothā€ fixes the problem even in the live ISO.

1 Like

Well, I’ve tried everything without success, I’m still having Bluetooth problems.
It worked flawlessly in Fedora 41, and despite multiple kernel updates, the problem remains. This bug significantly impacts usability for many of us, and it’s disheartening to consider switching distributions after using Fedora since version 36. I hope a definitive fix is released soon.

Are you using the systems built in wifi/bluetooth card or are you using a dongle? If it’s a wifi/bluetooth card can you put inxi -N into a terminal and paste the output so we can see what it is.

1 Like

Have you considered power management?

There have been many changes since I retired – Fedora seems to be using upowerd, and provides a tool (upower). Have a look at man upower, but that says ā€œTODO: not fully documentedā€. Also look at https://wiki.archlinux.org/title/Power_management, which provides a bash script that ā€œprints power settings and a variety of other properties for USB and PCI devicesā€.

I don’t think I can help about other things but I can help about this.

wpctl settings --save bluetooth.autoswitch-to-headset-profile false

Source: PipeWire - ArchWiki

1 Like

STILL NOT FIXED WITH KERNEL UPDATE 6.15.10-200.fc42.x86_64 (64-bit)

Here’s the output of inxi -N:

Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
    driver: rtw_8822ce

The problem seemed to occur again on Fedora 41 (on a downgraded system), although now the bluetooth mouse immediately reconnected when I tried moving it, whereas on Fedora 42 it remained disconnected for a longer time (even while moving it, which normally causes a reconnect).

I’ve downgraded bluetooth-related packages to the following versions on my Fedora 41 system, and I’m still evaluating whether this helps.

$ rpm -qa | grep ^blue
blueman-2.4.3-1.fc41.x86_64
bluez-5.78-1.fc41.x86_64
bluez-libs-5.78-1.fc41.x86_64
bluez-obexd-5.78-1.fc41.x86_64

For others here, bluetooth problems might be fixed with:

$ dnf downgrade 'bluez*' blueman

Futhermore, you MAY or MAY NOT need to re-create the bluetooth pairing as well. This fixed audio quality issues with some headphones, even after I had already downgraded my system to Fedora 41. Perhaps the /var/lib/bluetooth state files were changed by Fedora 42 in a way that caused problems, even after going back to Fedora 41. So perhaps re-creating the bluetooth pairing MAY or MAY NOT resolve the problem for Fedora 42 users, although @angel-edu says he tried that and it didn’t work for him. But for users who go back to Fedora 41, this may resolve certain issues.

I can finally use my mouse again without it disconnecting randomly. Hopefully it stays that way (I will post here if problems keep occurring). I might even skip Fedora 42 and eventually upgrade F41 → F42 → F43 (on the same day).

Since my last post (link), I haven’t had issues with bluetooth. I haven’t had to delete any /var/lib/bluetooth state files either. I ā€œonlyā€ downgraded to Fedora 41, then downgraded the bluetooth-related packages afterwards as well, and re-created the bluetooth pairings (by removing them and setting them up again).

So far, my mouse is only disconnecting due to normal behavior, which is when it automatically disconnects after 5 or 10 minutes of idleness.

But the constant disconnect problems that I had on Fedora 42 have, so far, not yet resurfaced.

Finger crossed. :crossed_fingers:

STILL NOT FIXED WITH KERNEL UPDATE 6.16.3-200.fc42.x86_64 (64-bit)

Okay, that’s it. I’m fed up. I’m done with this. Need to seriously have a look at debian now.

Have you tried downgrading the Realtek firmware? There is a bug report on Redhat’s Bugzilla for the RTL8822CE that the firmware back in 2022 didn’t work and downgrading it was the solution to fixing it. This may be the same case again.

There was a thread I responded to, two weeks ago, regarding the 8852BE chipset, but I found bug reports for flaky bluetooth related to 8852CE chipset. Your chipset is 8822CE. The reports I found for 8852* are in the provided link to the thread I was responding to. It’s possible that changes have also been made to the 8822CE firmware drivers that are causing similar issues. Commit history for 8822* can be found here.

For me, this can’t be it, as I’m using the Intel AX211 wifi/bluetooth adapter. lsusb lists it as: ID 8087:0033 Intel Corp. AX211 Bluetooth

Thanks for posting, though!

It seems that the issue has been resolved on my end because I haven’t experienced any Bluetooth disconnections today.

What I did was disable the power saving mode on my adapter, which, according to my model (rtw89), has problems because the WirePlumber management was changed.

I’m leaving the changes I made, in case anyone has the same model and is experiencing the same Bluetooth disconnection issues.

  1. First, I checked my Wi-Fi/Bluetooth chip model:
lspci -knn | grep -i net -A 3

Captura de pantalla_20250905_131549

Next, disabled Wi-Fi power saving at NetworkManager level:

sudo nano /etc/NetworkManager/conf.d/default-wifi-powersave-off.conf

Put in:

[connection]
wifi.powersave = 2

Then:

sudo systemctl restart NetworkManager
  1. Disabled Realtek driver internal power save:

Created a driver config file:

sudo nano /etc/modprobe.d/70-rtw89.conf

Put in:

options rtw89_pci disable_aspm=Y
options rtw89_core disable_ps_mode=Y

Then updated initramfs (optional but recommended) and rebooted:

sudo dracut -f
sudo reboot

So far, I haven’t had any disconnections with my Bluetooth headphones in any profile (SBC or ACC). I’ll let you know how it goes.

UPDATE: I am able to reproduce the issue on the latest endeavourOS Ganymede ISO.

Probably a KDE issue? :sob:
When I reported my first issue (https://discussion.fedoraproject.org/t/bluetooth-is-extremely-bugged-out-in-f42-kde-also-in-f41-kde), I tested it on openSUSE Tumbleweed latest snapshot of that time & also endeavour. Bluetooth worked fine in both.

I will also try this out on the latest openSUSE Tumbleweed ISO (current) AGAIN and post the result.