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

Some scenarios I faced:

  1. Connect my bluetooth headset using Bluetooth, and it disconnects immediately after connection. There are forums posts that say after minutes or a minute, but mine is instant.
  2. Problem 1 is fixed by restarting bluetooth but appears again after EVERY reboot.
  3. Sometimes, logging out and logging in (while Bluetooth connected) makes the “High Fidelity Playback, A2DP” stuff disappear. The sound is extremely baffled and sounds like Handsfree audio (I think it is, Handsfree audio)

A simple sudo systemctl restart bluetooth fixes EVERY issue everytime, but I’m curious if this is a bug. Also, I’ve tried to forget the device and add it again, but that never seemed to help. I had to restart bluetooth.
Also, I had the same problem on a disk install of Ultramarine 41 KDE, which is based on Fedora 41. Now running stock Fedora 42 KDE, same issue.

I face some Bluetooth issues too. It automatically turns itself off and won’t turn on until I restart it with sudo systemctl restart bluetooth . There aren’t any issues apart from this no audio issue, not to my notice.

Hi, what is your headset?

ah just regular headband: realme wireless 3 i think

Same for me on Fedora 42. I’m experiencing random disconnections. I thought a kernel update would resolve the issue, but it hasn’t.
The issue is only resolved temporarily by entering “sudo systemctl restart bluetooth.” The problem recurs shortly after.
I traced it to see what was causing it, and it turns out the disconnections happened mostly when I opened a browser.

I’m having this issue as well, but only for a specific bluetooth device (Vizo V21d soundbar) and only when I attempt to play media.

The device will initially connect, I’ll attempt to play audio, and it will immediately disconnect.

Does running sudo systemctl restart bluetooth and then connecting again resolve the problem?

No, unfortunately. Nor did clearing cache for pipewire or wireplumber, or downgrading bluez (per another discussion I found).

My problem seems consistent with an incompatible, codec but I haven’t been able to narrow it down.

Manually connecting with bluetoothctl:

[CHG] Device 84:D3:52:7A:62:7F Connected: yes
[NEW] Endpoint /org/bluez/hci0/dev_84_D3_52_7A_62_7F/sep1 
[NEW] Transport /org/bluez/hci0/dev_84_D3_52_7A_62_7F/sep1/fd2 
[CHG] Device 84:D3:52:7A:62:7F ServicesResolved: yes

Then playing media:

[CHG] Transport /org/bluez/hci0/dev_84_D3_52_7A_62_7F/sep1/fd2 State: active
[CHG] Device 84:D3:52:7A:62:7F ServicesResolved: no
[SIGNAL] org.bluez.Device1.Disconnected org.bluez.Reason.Remote Connection terminated by remote user
[CHG] Device 84:D3:52:7A:62:7F Connected: no
[DEL] Transport /org/bluez/hci0/dev_84_D3_52_7A_62_7F/sep1/fd2 
[DEL] Endpoint /org/bluez/hci0/dev_84_D3_52_7A_62_7F/sep1

This happened before and after adding a configuration to ~/.config/wireplumber/bluetooth.lua.d/ to force SBC fallback.

After searching through different threads and trying everything, nothing worked, I leave the details of the problem:
Summary:
Bluetooth audio randomly disconnects and reconnects in Fedora 42 KDE regardless of adapter or headphones

Description:
Since upgrading to Fedora 42, I have been experiencing severe Bluetooth audio issues that did not occur in previous Fedora releases. The problem happens with both my laptop’s internal Bluetooth adapter and an external USB dongle, and with all my Bluetooth headphones (new and old models).
I am using KDE Plasma as my desktop environment.

What happens:

  • When I play any multimedia content (music, video, YouTube, etc.), the Bluetooth connection randomly disconnects and reconnects by itself. The audio is interrupted and sometimes the device reconnects automatically, but the problem keeps repeating.
  • This happens with all my Bluetooth headphones, not just one model.
  • The issue is present with both the built-in Bluetooth and a USB dongle (different chipsets).
  • The only workaround is to run sudo systemctl restart bluetooth. Sometimes, I have to run this command several times in a row (after each disconnection) until, for some reason, the connection stabilizes and I can use my headphones normally for the rest of the session. However, after a reboot or the next day, the problem returns and I have to repeat the process.

What I tried:

  • Forgetting and re-pairing devices
  • Using different headphones and adapters
  • Changing audio profiles in KDE/Plasma (SBC, AAC)

Logs:
Here are some logs from my system when my headphones disconnect, collected with journalctl -xe | grep bluetooth and during/after the issue:

journalctl -xe | grep bluetooth
jul 29 17:04:16 fedora bluetoothd[109721]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
jul 29 17:04:37 fedora bluetoothd[109721]: /org/bluez/hci0/dev_F9_3C_16_14_77_2D/sep2/fd6: fd(40) ready
jul 29 17:07:45 fedora bluetoothd[109721]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
jul 29 17:07:51 fedora bluetoothd[109721]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
jul 29 17:07:53 fedora bluetoothd[109721]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for F9:3C:16:14:77:2D: Device or resource busy
jul 29 17:07:53 fedora bluetoothd[109721]: plugins/policy.c:reconnect_timeout() Reconnecting services failed: Device or resource busy (16)
jul 29 17:07:55 fedora bluetoothd[109721]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for F9:3C:16:14:77:2D: Device or resource busy

System details:

  • Fedora version: 42
  • Kernel version: 6.15.7-200.fc42.x86_64
  • BlueZ version: 5.83-2.fc42.x86_64
  • PipeWire version: 1.4.7-1.fc42.x86_64
  • Desktop: KDE Plasma

For what it’s worth, Bluetooth issues don’t seem to be exclusive to KDE Plasma. It seems many of us are experiencing different effects, though - perhaps related to the same package(s).

I’m on Gnome and still having the problems that I shared previously and, like you, didn’t have any issues prior to a fairly recent update.

1 Like

Still not fixed with Kernel Upgrade 6.15.8-200.fc42.x86_64 (64-bit)

2 Likes

I also updated the kernel to 6.15.8, but the disconnection errors have decreased, although I still experience them to a lesser extent.
I’m going to try clearing the cache to see if that solves the problem.

Nice! Just got the Kernel upgrade and my issue seems completely resolved after clearing cache & rebooting.

Will update if any other problems arise.

1 Like

In my case, after updating the kernel and clearing the Bluetooth cache, the problem persists but occurs less frequently, and I experience temporary disconnections when I open a browser…

$ journalctl -xe | grep bluetooth
jul 30 17:18:14 fedora bluetoothd[1041]: /org/bluez/hci0/dev_F9_3C_16_14_77_2D/sep1/fd3: fd(41) ready
jul 30 17:30:03 fedora bluetoothd[1041]: profiles/audio/avdtp.c:cancel_request() Suspend: Connection timed out (110)
jul 30 17:30:05 fedora bluetoothd[1041]: profiles/audio/avdtp.c:handle_unanswered_req() No reply to Suspend request
jul 30 17:30:05 fedora bluetoothd[1041]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
jul 30 17:30:11 fedora bluetoothd[1041]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
jul 30 17:30:18 fedora bluetoothd[1041]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
jul 30 17:30:22 fedora bluetoothd[1041]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for F9:3C:16:14:77:2D: Device or resource busy
jul 30 17:30:22 fedora bluetoothd[1041]: plugins/policy.c:reconnect_timeout() Reconnecting services failed: Device or resource busy (16)
jul 30 17:30:23 fedora bluetoothd[1041]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for F9:3C:16:14:77:2D: Device or resource busy
jul 30 17:30:27 fedora bluetoothd[1041]: /org/bluez/hci0/dev_F9_3C_16_14_77_2D/sep1/fd5: fd(41) ready
jul 30 18:30:41 fedora bluetoothd[1041]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
jul 30 18:31:35 fedora bluetoothd[1041]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
jul 30 18:31:41 fedora bluetoothd[1041]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down

Nevermind, the issue returned today. Clearing the cache doesn’t help.

:frowning:

What really frustrates me is that Bluetooth was working perfectly on Fedora 41, but as soon as I upgraded to Fedora 42, everything broke. Since then, no kernel update has fixed the problem, and it’s been going on for quite a while now.

Interesting. Mine hasn’t had any problems since update.

Does your journal say anything?

1 Like

I’m getting these errors:
image

I tried to forget the device & add it again, still same issue. This is what my journal shows:

Aug 02 13:09:10 fedora systemd[1446]: Reached target bluetooth.target - Bluetooth.
Aug 02 13:09:17 fedora bluetoothd[1078]: No matching connection for device
Aug 02 13:11:12 fedora bluetoothd[1078]: No matching connection for device
Aug 02 13:13:07 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/ForgetDeviceDialog.qml:35: TypeError: Cannot read property 'name' of null
Aug 02 13:13:07 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/ForgetDeviceDialog.qml:75: TypeError: Cannot read property 'adapter' of null
Aug 02 13:13:07 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/ForgetDeviceAction.qml:17: TypeError: Cannot read property 'name' of null
Aug 02 13:13:10 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/ForgetDeviceDialog.qml:35: TypeError: Cannot read property 'name' of null
Aug 02 13:13:10 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/ForgetDeviceDialog.qml:75: TypeError: Cannot read property 'adapter' of null
Aug 02 13:13:10 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/ForgetDeviceAction.qml:17: TypeError: Cannot read property 'name' of null
Aug 02 13:13:53 fedora bluetoothd[1078]: No matching connection for device
Aug 02 13:14:03 fedora bluetoothd[1078]: No matching connection for device

After running sudo systemctl restart bluetooth, the issue is fixed, and here’s the journal:

Aug 02 13:15:55 fedora bluetoothd[1078]: No matching connection for device
Aug 02 13:16:10 fedora sudo[7256]:  pb-mint : TTY=pts/1 ; PWD=/home/pb-mint ; USER=root ; COMMAND=/usr/sbin/systemctl restart bluetooth
Aug 02 13:16:11 fedora bluetoothd[1078]: Terminating
Aug 02 13:16:11 fedora systemd[1]: Stopping bluetooth.service - Bluetooth service...
░░ Subject: A stop job for unit bluetooth.service has begun execution
░░ A stop job for unit bluetooth.service has begun execution.
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSource/ldac
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSink/aac
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSource/aac
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSink/opus_g
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSource/opus_g
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSink/sbc
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSource/sbc
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSource/faststream
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSource/faststream_duplex
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSink/opus_05
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSource/opus_05
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Aug 02 13:16:11 fedora bluetoothd[1078]: Endpoint unregistered: sender=:1.58 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Aug 02 13:16:11 fedora bluetoothd[1078]: Battery Provider Manager destroyed
Aug 02 13:16:11 fedora bluetoothd[1078]: Stopping SDP server
Aug 02 13:16:11 fedora bluetoothd[1078]: Exit
Aug 02 13:16:11 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/General.qml:60: TypeError: Cannot read property 'discoverable' of null
Aug 02 13:16:11 fedora systemd[1]: bluetooth.service: Deactivated successfully.
░░ The unit bluetooth.service has successfully entered the 'dead' state.
Aug 02 13:16:11 fedora systemd[1]: Stopped bluetooth.service - Bluetooth service.
░░ Subject: A stop job for unit bluetooth.service has finished
░░ A stop job for unit bluetooth.service has finished.
Aug 02 13:16:11 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/General.qml:54: TypeError: Cannot read property 'powered' of null
Aug 02 13:16:11 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/General.qml:48: TypeError: Cannot read property 'address' of null
Aug 02 13:16:11 fedora systemsettings[5706]: qrc:/kcm/kcm_bluetooth/General.qml:42: TypeError: Cannot read property 'name' of null
Aug 02 13:16:11 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 02 13:16:11 fedora systemd[1]: Starting bluetooth.service - Bluetooth service...
░░ Subject: A start job for unit bluetooth.service has begun execution
░░ A start job for unit bluetooth.service has begun execution.
Aug 02 13:16:11 fedora bluetoothd[7303]: Bluetooth daemon 5.83
Aug 02 13:16:11 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 02 13:16:11 fedora systemd[1]: Started bluetooth.service - Bluetooth service.
░░ Subject: A start job for unit bluetooth.service has finished successfully
░░ A start job for unit bluetooth.service has finished successfully.
Aug 02 13:16:11 fedora bluetoothd[7303]: Starting SDP server
Aug 02 13:16:11 fedora bluetoothd[7303]: Bluetooth management interface 1.23 initialized
Aug 02 13:16:11 fedora bluetoothd[7303]: Battery Provider Manager created
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/ldac
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/aac
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/aac
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/opus_g
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/opus_g
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/sbc
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/sbc
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/faststream
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/faststream_duplex
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/opus_05
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/opus_05
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Aug 02 13:16:11 fedora bluetoothd[7303]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Aug 02 13:16:16 fedora systemd[7269]: Reached target bluetooth.target - Bluetooth.
Aug 02 13:16:22 fedora systemd[7269]: Stopped target bluetooth.target - Bluetooth.

Having many random disconnects here on Fedora 42. This did NOT happen as much on Fedora 41. On Fedora 41, in my experience, if a device had a connection, the connection remained largely stable. On Fedora 42 however, I see regular disconnects. If I have the bluetoothctl prompt open, there’s no reason given for the disconnect at all.

Update: Here’s my output of bluetoothctl whilst connecting the device & it automatically getting disconnected:

[NEW] Media /org/bluez/hci0 
        SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
        SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Device 41:42:8E:52:DA:13 Connected: yes
[NEW] Endpoint /org/bluez/hci0/dev_41_42_8E_52_DA_13/sep1 
[NEW] Endpoint /org/bluez/hci0/dev_41_42_8E_52_DA_13/sep2 
[NEW] Transport /org/bluez/hci0/dev_41_42_8E_52_DA_13/sep2/fd1 
[CHG] Transport /org/bluez/hci0/dev_41_42_8E_52_DA_13/sep2/fd1 Volume: 0x0058 (88)
[CHG] Device 41:42:8E:52:DA:13 ServicesResolved: yes
[DEL] Transport /org/bluez/hci0/dev_41_42_8E_52_DA_13/sep2/fd1 
[DEL] Endpoint /org/bluez/hci0/dev_41_42_8E_52_DA_13/sep1 
[DEL] Endpoint /org/bluez/hci0/dev_41_42_8E_52_DA_13/sep2 
[CHG] Device 41:42:8E:52:DA:13 ServicesResolved: no
[SIGNAL] org.bluez.Device1.Disconnected org.bluez.Reason.Local Connection terminated by local host
[CHG] Device 41:42:8E:52:DA:13 Connected: no