Bazzite 43 bluetooth issue

Bazzite
1

Recently I upgraded my PC to bazzite 43 and my headphones Baseus H1 Pro autodisconnect themselves for no apparent reason. I’m using baseus bt dongle to connect my pc to headphones. Bluetoothctl gives me this output

[CHG] Device 41:AA:00:A1:EF:88 Connected: yes
[NEW] Endpoint /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep1
[NEW] Endpoint /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep2
[NEW] Endpoint /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep4
[NEW] Transport /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep2/fd1
[CHG] Transport /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep2/fd1 Delay: 0x0898 (2200)
[CHG] Transport /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep2/fd1 Volume: 0x0045 (69)
[CHG] Device 41:AA:00:A1:EF:88 ServicesResolved: yes
[DEL] Transport /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep2/fd1
[DEL] Endpoint /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep1
[DEL] Endpoint /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep2
[DEL] Endpoint /org/bluez/hci0/dev_41_AA_00_A1_EF_88/sep4
[CHG] Device 41:AA:00:A1:EF:88 ServicesResolved: no
[SIGNAL] BREDR.Disconnected - org.bluez.Reason.Remote, Connection terminated by remote user
[SIGNAL] Disconnected - org.bluez.Reason.Remote, Connection terminated by remote user
[CHG] Device 41:AA:00:A1:EF:88 Connected: no

The problem seems to go away after restarting all services with
sudo systemctl stop bluetooth
sudo rm -rf /var/lib/bluetooth/*
sudo systemctl start bluetooth
systemctl --user restart pipewire wireplumber\

If anyone knows what seems to be a problem I’ll be glad for an explanation how to fix it

2

@rzeczyspisane when you mentioned you were using a dongle that brought back memories (nightmares actually) of the years I spent using a wired USB headset to attend meetings in WebEx, etc.

There was a common hw bug commonly known as the “longer than 1 hour meeting USB issue”. A lot of us came to the conclusion that some USB controller / bridge chip was overheating when in constant use for more than an hour.

The workaround was to unplug from the USB port, wait 10 secs or so (presumably to allow the chip to cool a little and the firmware to detect the new cooled state) and then plug it back in.

I hope that is not the case for your sake, but you might try to unplug your USB dongle, wait some # secs and plug it back in. If you are not able to reconnect then what I am describing might not be related to the problem.

If that does work, then I am afraid the long term solution will be to eliminate the use of the dongle - for example, by using a dedicated bluetooth expansion card on the PCI bus instead.

Hopefully others will have a better answer for you. But I thought I would share my experience from the past …

3

I doubt that might be the case since the problem is present even after a cold boot

This dongle actually worked flawlessly during bazzite 42 cadence, but after upgrading to 43 problem have started

After researching a little I came to conclusion that this might be a kde+bluez bug.

It affects some headsets so it is a minor regression, but still that’s annoying