Bazzite 43 bluetooth problems

[Devs21X]

Describe the bug

After updating my laptop from Bazzite 42 to Bazzite 43, the integrated bluetooth of my laptop stopped working correctly. Whenever I try to connect any of my bluetooth mouses they just keeps disconnecting, looking at the terminal with bluetoothctl it throws this error repeatedly:

• [SIGNAL] LE.Disconnected - org.bluez.Reason.Timeout, Connection timeout
• [SIGNAL] Disconnected - org.bluez.Reason.Timeout, Connection timeout

What did you expect to happen?

To be able to connect my bluetooth mouses like it was with Bazzite 42

Session Logs

bluetoothctl
[NEW] Media /org/bluez/hci0
	SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
	SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 80:91:33:3A:21:70 Discovering: yes
[NEW] Device D5:E0:4B:54:7B:3F Pebble M350s
[NEW] Device 22:DF:8B:5E:DB:D6 22-DF-8B-5E-DB-D6
[NEW] Device 2C:D4:26:A0:EB:E7 2C-D4-26-A0-EB-E7
[CHG] Device 22:DF:8B:5E:DB:D6 RSSI: 0xffffffb4 (-76)
[CHG] Device D5:E0:4B:54:7B:3F RSSI: 0xffffffc9 (-55)
[CHG] Device 2C:D4:26:A0:EB:E7 RSSI is nil
[CHG] Device 22:DF:8B:5E:DB:D6 RSSI is nil
[CHG] Device D5:E0:4B:54:7B:3F TxPower is nil
[CHG] Device D5:E0:4B:54:7B:3F RSSI is nil
[CHG] Controller 80:91:33:3A:21:70 Discovering: no
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[CHG] Device D5:E0:4B:54:7B:3F Bonded: yes
[CHG] Controller 80:91:33:3A:21:70 Discovering: yes
[CHG] Device D5:E0:4B:54:7B:3F WakeAllowed: yes
[SIGNAL] LE.Disconnected - org.bluez.Reason.Unknown, Unspecified
[SIGNAL] Disconnected - org.bluez.Reason.Unknown, Unspecified
[CHG] Device D5:E0:4B:54:7B:3F Connected: no
[CHG] Device D5:E0:4B:54:7B:3F Paired: yes
[CHG] Device D5:E0:4B:54:7B:3F Trusted: yes
[CHG] Device D5:E0:4B:54:7B:3F WakeAllowed: yes
[NEW] Device E4:DB:6D:AD:75:9A MIBOX S
[CHG] Device E4:DB:6D:AD:75:9A RSSI: 0xffffffc5 (-59)
[CHG] Device E4:DB:6D:AD:75:9A RSSI: 0xffffffc6 (-58)
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[SIGNAL] LE.Disconnected - org.bluez.Reason.Unknown, Unspecified
[SIGNAL] Disconnected - org.bluez.Reason.Unknown, Unspecified
[CHG] Device D5:E0:4B:54:7B:3F Connected: no
[DEL] Device 2C:D4:26:A0:EB:E7 2C-D4-26-A0-EB-E7
[DEL] Device 22:DF:8B:5E:DB:D6 22-DF-8B-5E-DB-D6
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[CHG] Device E4:DB:6D:AD:75:9A RSSI: 0xffffffc2 (-62)
[NEW] Primary Service (Handle 0x0001)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0001
	00001800-0000-1000-8000-00805f9b34fb
	Generic Access Profile
[NEW] Characteristic (Handle 0x0002)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0001/char0002
	00002a00-0000-1000-8000-00805f9b34fb
	Device Name
[NEW] Characteristic (Handle 0x0004)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0001/char0004
	00002a01-0000-1000-8000-00805f9b34fb
	Appearance
[NEW] Characteristic (Handle 0x0006)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0001/char0006
	00002a04-0000-1000-8000-00805f9b34fb
	Peripheral Preferred Connection Parameters
[NEW] Primary Service (Handle 0x000a)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000a
	00001801-0000-1000-8000-00805f9b34fb
	Generic Attribute Profile
[NEW] Characteristic (Handle 0x000b)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000a/char000b
	00002a05-0000-1000-8000-00805f9b34fb
	Service Changed
[NEW] Descriptor (Handle 0x000d)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000a/char000b/desc000d
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Primary Service (Handle 0x000e)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000e
	0000180a-0000-1000-8000-00805f9b34fb
	Device Information
[NEW] Characteristic (Handle 0x000f)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000e/char000f
	00002a29-0000-1000-8000-00805f9b34fb
	Manufacturer Name String
[NEW] Characteristic (Handle 0x0011)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000e/char0011
	00002a24-0000-1000-8000-00805f9b34fb
	Model Number String
[NEW] Characteristic (Handle 0x0013)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000e/char0013
	00002a25-0000-1000-8000-00805f9b34fb
	Serial Number String
[NEW] Characteristic (Handle 0x0015)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000e/char0015
	00002a26-0000-1000-8000-00805f9b34fb
	Firmware Revision String
[NEW] Characteristic (Handle 0x0017)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000e/char0017
	00002a28-0000-1000-8000-00805f9b34fb
	Software Revision String
[NEW] Characteristic (Handle 0x0019)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service000e/char0019
	00002a50-0000-1000-8000-00805f9b34fb
	PnP ID
[NEW] Primary Service (Handle 0x001b)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001b
	0000180f-0000-1000-8000-00805f9b34fb
	Battery Service
[NEW] Characteristic (Handle 0x001c)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001b/char001c
	00002a19-0000-1000-8000-00805f9b34fb
	Battery Level
[NEW] Descriptor (Handle 0x001e)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001b/char001c/desc001e
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Primary Service (Handle 0x001f)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f
	00001812-0000-1000-8000-00805f9b34fb
	Human Interface Device
[NEW] Characteristic (Handle 0x0020)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char0020
	00002a4a-0000-1000-8000-00805f9b34fb
	HID Information
[NEW] Characteristic (Handle 0x0022)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char0022
	00002a33-0000-1000-8000-00805f9b34fb
	Boot Mouse Input Report
[NEW] Descriptor (Handle 0x0024)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char0022/desc0024
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Characteristic (Handle 0x0025)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char0025
	00002a4b-0000-1000-8000-00805f9b34fb
	Report Map
[NEW] Characteristic (Handle 0x0027)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char0027
	00002a4d-0000-1000-8000-00805f9b34fb
	Report
[NEW] Descriptor (Handle 0x0029)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char0027/desc0029
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Descriptor (Handle 0x002a)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char0027/desc002a
	00002908-0000-1000-8000-00805f9b34fb
	Report Reference
[NEW] Characteristic (Handle 0x002b)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char002b
	00002a4d-0000-1000-8000-00805f9b34fb
	Report
[NEW] Descriptor (Handle 0x002d)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char002b/desc002d
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Descriptor (Handle 0x002e)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char002b/desc002e
	00002908-0000-1000-8000-00805f9b34fb
	Report Reference
[NEW] Characteristic (Handle 0x002f)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char002f
	00002a4d-0000-1000-8000-00805f9b34fb
	Report
[NEW] Descriptor (Handle 0x0031)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char002f/desc0031
	00002908-0000-1000-8000-00805f9b34fb
	Report Reference
[NEW] Characteristic (Handle 0x0032)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char0032
	00002a4c-0000-1000-8000-00805f9b34fb
	HID Control Point
[NEW] Characteristic (Handle 0x0034)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service001f/char0034
	00002a4e-0000-1000-8000-00805f9b34fb
	Protocol Mode
[NEW] Primary Service (Handle 0x0036)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0036
	0000fd72-0000-1000-8000-00805f9b34fb
	Logitech International SA
[NEW] Characteristic (Handle 0x0037)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0036/char0037
	fd720001-0000-1000-8000-011f2000046d
	Vendor specific
[NEW] Characteristic (Handle 0x0039)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0036/char0039
	fd720002-0000-1000-8000-011f2000046d
	Vendor specific
[NEW] Characteristic (Handle 0x003b)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0036/char003b
	fd720003-0000-1000-8000-011f2000046d
	Vendor specific
[NEW] Characteristic (Handle 0x003d)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0036/char003d
	fd720004-0000-1000-8000-011f2000046d
	Vendor specific
[NEW] Characteristic (Handle 0x003f)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0036/char003f
	fd720005-0000-1000-8000-011f2000046d
	Vendor specific
[NEW] Characteristic (Handle 0x0041)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0036/char0041
	fd720006-0000-1000-8000-011f2000046d
	Vendor specific
[NEW] Primary Service (Handle 0x0043)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0043
	00010000-0000-1000-8000-011f2000046d
	Vendor specific
[NEW] Characteristic (Handle 0x0044)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0043/char0044
	00010001-0000-1000-8000-011f2000046d
	Vendor specific
[NEW] Descriptor (Handle 0x0046)
	/org/bluez/hci0/dev_D5_E0_4B_54_7B_3F/service0043/char0044/desc0046
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[CHG] Device D5:E0:4B:54:7B:3F UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D5:E0:4B:54:7B:3F UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D5:E0:4B:54:7B:3F UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D5:E0:4B:54:7B:3F UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D5:E0:4B:54:7B:3F UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D5:E0:4B:54:7B:3F UUIDs: 0000fd72-0000-1000-8000-00805f9b34fb
[CHG] Device D5:E0:4B:54:7B:3F UUIDs: 00010000-0000-1000-8000-011f2000046d
[CHG] Device D5:E0:4B:54:7B:3F ServicesResolved: yes
[CHG] Device D5:E0:4B:54:7B:3F Modalias: usb:v046DpB036d0007
[CHG] Device D5:E0:4B:54:7B:3F ServicesResolved: no
[SIGNAL] LE.Disconnected - org.bluez.Reason.Timeout, Connection timeout
[SIGNAL] Disconnected - org.bluez.Reason.Timeout, Connection timeout
[CHG] Device D5:E0:4B:54:7B:3F Connected: no
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[SIGNAL] LE.Disconnected - org.bluez.Reason.Timeout, Connection timeout
[SIGNAL] Disconnected - org.bluez.Reason.Timeout, Connection timeout
[CHG] Device D5:E0:4B:54:7B:3F Connected: no
[CHG] Device E4:DB:6D:AD:75:9A RSSI: 0xffffffc4 (-60)
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[SIGNAL] LE.Disconnected - org.bluez.Reason.Timeout, Connection timeout
[SIGNAL] Disconnected - org.bluez.Reason.Timeout, Connection timeout
[CHG] Device D5:E0:4B:54:7B:3F Connected: no
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[CHG] Device E4:DB:6D:AD:75:9A RSSI: 0xffffffc5 (-59)
[SIGNAL] LE.Disconnected - org.bluez.Reason.Timeout, Connection timeout
[SIGNAL] Disconnected - org.bluez.Reason.Timeout, Connection timeout
[CHG] Device D5:E0:4B:54:7B:3F Connected: no
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[CHG] Device E4:DB:6D:AD:75:9A RSSI: 0xffffffca (-54)
[SIGNAL] LE.Disconnected - org.bluez.Reason.Timeout, Connection timeout
[SIGNAL] Disconnected - org.bluez.Reason.Timeout, Connection timeout
[CHG] Device D5:E0:4B:54:7B:3F Connected: no
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[SIGNAL] LE.Disconnected - org.bluez.Reason.Timeout, Connection timeout
[SIGNAL] Disconnected - org.bluez.Reason.Timeout, Connection timeout
[CHG] Device D5:E0:4B:54:7B:3F Connected: no
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[CHG] Device E4:DB:6D:AD:75:9A RSSI: 0xffffffc3 (-61)
[SIGNAL] LE.Disconnected - org.bluez.Reason.Timeout, Connection timeout
[SIGNAL] Disconnected - org.bluez.Reason.Timeout, Connection timeout
[CHG] Device D5:E0:4B:54:7B:3F Connected: no
[CHG] Device E4:DB:6D:AD:75:9A RSSI: 0xffffffc4 (-60)
[CHG] Device D5:E0:4B:54:7B:3F Connected: yes
[CHG] Device E4:DB:6D:AD:75:9A RSSI: 0xffffffc8 (-56)
[SIGNAL] LE.Disconnected - org.bluez.Reason.Timeout, Connection timeout
[SIGNAL] Disconnected - org.bluez.Reason.Timeout, Connection timeout
[CHG] Device D5:E0:4B:54:7B:3F Connected: no

Hardware

• Laptop ASUS VivoBook X512DA
• CPU AMD Ryzen 5 3500U
• GPU AMD Radeon Vega 8 Graphics
• RAM 12 GB
• SSD 512 GB

Extra information or context

My mouses are both Logitech, a Peeble Mouse 2 M350s and a Logi Pop Mouse.
I tested connecting them with the USB bluetooth adapter that I use on my desktop PC (TP-Link UB5A) and they worked fine with that adapter, the problem is only with the internal adapter of my laptop.

In Bazzite 42 I tested with the following kernels, bluetooth works fine in these versions:

• 6.16.4-116.bazzite.fc42.x86_64 (My previous installation)
• 6.16.12-200.fc42.x86_64 (From an older live USB)

And in Bazzite 43 I tested with the following kernels, bluetooth doesn't work in these versions:

• 6.17.7-ba22.fc43.x86_64 (After updating my previous installation)
• 6.17.12-300.fc43.x86_64 (From a recent live USB)

[samyang211]

I have the same issue. My host is G7pt, and the network card is MT7925B

[sumitkm]

Just updated to 43 and my Logitech Lift stopped working. It was listed but not connected. I removed it, put it in pairing mode, but it won't appear for re-pairing.

Funnily enough, the headphones continue to work over Bluetooth.

[jackster1209]

+1

Having bluetooth issues with any bluetooth gamepad I have tried so far.

[Catarek]

Similar issues
#3812

with cachyos as well
https://discuss.cachyos.org/t/bluetooth-connection-disconnection-cycling/20027/20

[yeswalrus]

Similar issues here. I just tried using bluetooth to connect to a wireless headset and it keeps giving me 'Setup failed'. MB is MSI x870 Tomahawk WIFI.

Update: Nevermind. The pairing wizard kept disconnecting, but if I try and connect via the bluetooth menu in system settings it seems to be fine

bluetoothctl
[NEW] Media /org/bluez/hci0 
	SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
	SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Device 28:9A:4B:19:6B:BE RSSI: 0xffffffc3 (-61)
[CHG] Device 28:9A:4B:19:6B:BE Connected: yes
[CHG] Device 28:9A:4B:19:6B:BE Bonded: yes
[CHG] Device 28:9A:4B:19:6B:BE UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 28:9A:4B:19:6B:BE UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 28:9A:4B:19:6B:BE UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 28:9A:4B:19:6B:BE UUIDs: 0000110d-0000-1000-8000-00805f9b34fb
[CHG] Device 28:9A:4B:19:6B:BE UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 28:9A:4B:19:6B:BE UUIDs: 0000110f-0000-1000-8000-00805f9b34fb
[CHG] Device 28:9A:4B:19:6B:BE UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 28:9A:4B:19:6B:BE UUIDs: 00001131-0000-1000-8000-00805f9b34fb
[CHG] Device 28:9A:4B:19:6B:BE UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 28:9A:4B:19:6B:BE ServicesResolved: yes
[CHG] Device 28:9A:4B:19:6B:BE Paired: yes
[CHG] Device 28:9A:4B:19:6B:BE ServicesResolved: no
[SIGNAL] BREDR.Disconnected - org.bluez.Reason.Local, Connection terminated by local host
[SIGNAL] Disconnected - org.bluez.Reason.Local, Connection terminated by local host
[CHG] Device 28:9A:4B:19:6B:BE Connected: no
[CHG] Device 28:9A:4B:19:6B:BE Trusted: yes

[drandom3]

Same issue for me. My logitech MX keyboard just stopped connecting

[sumitkm]

Anyone knows how we can try latest version of Bluez on Bazzite? Looks like Bazzite is currently one version off Bluez. They have similar bugs in older versions but I can't tell if there's anything in x.81 that's fixed in x.82

[Grondsmite]

Similar issues here. I used steps in thread https://github.com/ublue-os/bazzite/issues/1899 to some success with headphones, but the keyboard is having issues with org.blue...

[bluetoothctl]> version
Version 5.84
[NEW] Device F4:EE:25:E4:C7:C8 AKKO 3098-3
[CHG] Device F4:EE:25:E4:C7:C8 RSSI: 0xffffffa5 (-91)
[bluetoothctl]> unblock F4:EE:25:E4:C7:C8
Changing F4:EE:25:E4:C7:C8 unblock succeeded
[bluetoothctl]> trust F4:EE:25:E4:C7:C8
[CHG] Device F4:EE:25:E4:C7:C8 Trusted: yes
Changing F4:EE:25:E4:C7:C8 trust succeeded
[bluetoothctl]> connect F4:EE:25:E4:C7:C8
Attempting to connect to F4:EE:25:E4:C7:C8
[CHG] Device B4:EE:25:E1:C5:C8 RSSI: 0xffffffa6 (-90)
[CHG] Device F4:EE:25:E4:C7:C8 Connected: yes
Failed to connect: org.bluez.Error.Failed le-connection-abort-by-local
[SIGNAL] LE.Disconnected - org.bluez.Reason.Unknown, Unspecified
[SIGNAL] Disconnected - org.bluez.Reason.Unknown, Unspecified
[CHG] Device F4:EE:25:E4:C7:C8 Connected: no
[CHG] Device F4:EE:25:E4:C7:C8 Connected: yes
[SIGNAL] LE.Disconnected - org.bluez.Reason.Unknown, Unspecified
[SIGNAL] Disconnected - org.bluez.Reason.Unknown, Unspecified
[CHG] Device F4:EE:25:E4:C7:C8 Connected: no
[CHG] Device F4:EE:25:E4:C7:C8 Connected: yes

This connect/disconnect continues with connecting and disconnecting.

[LZeugirdor]

+1 also have bluetooth disconnection issues.

[Catarek]

I disabled usb autosuspend. And it kinda solved my problem

rpm-ostree kargs --append-if-missing="usbcore.autosuspend=-1"

[LZeugirdor]

I disabled usb autosuspend. And it kinda solved my problem

rpm-ostree kargs --append-if-missing="usbcore.autosuspend=-1"

I was thinking about this because windows had a feature i needed to disable called usb auto suspend and it would cause issues with other usb devices as well like my DAC would drop out or reset volume and it was horrible. I might give this a try.

[LZeugirdor]

I tried and it hasn't fixed it completely. I still get at least one disconnect after 30 minutes ish

[AnharHussainMiah]

+1

Similar issues when connecting a PS4 controller (cheap clone, not original) it will pair and work the first time, but as soon as the controller is switched off, while it is still listed you can not connect to it. Even after switching bluetooth on/off and even rebooting the PC. The only way is to "forget" the paired device and re-pair again.

I know the controller is not the issue as it works flawlessly with my Amazon 4K Firestick.

[drandom3]

I recently swapped from Bazzite KDE to GNOME, and I no longer get this issue. Hope this helps you solve it!

[Devs21X]

I've just updated my laptop to Bazzite 44 (6.19.14-ogc1.1.fc44.x86_64) and I no longer have problems with my laptop's integrated bluetooth. I've tested with many bluetooth devices (mouse, keyboard, speakers, gamepads) and everything is working fine now.
Just for the record, I'm using Bazzite with KDE, so maybe the desktop environment is not relevant to the bluetooth functioning.
I'm closing this issue as resolved, as everything is working fine for me now.