Bug 482597 - Unable to pair headphone (mi buds) using KDE Bluetooth pairing wizard (bluetoothctl works)
Summary: Unable to pair headphone (mi buds) using KDE Bluetooth pairing wizard (blueto...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Bluetooth in general (other bugs)
Version First Reported In: 6.2.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Rosca
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-06 22:08 UTC by Marcelo Bossoni
Modified: 2025-05-27 17:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
bluetoothctl logs (6.18 KB, text/plain)
2025-01-14 23:14 UTC, Marcelo Bossoni
Details
logs with connect call only (18.27 KB, text/plain)
2025-01-14 23:20 UTC, Marcelo Bossoni
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcelo Bossoni 2024-03-06 22:08:28 UTC
SUMMARY
I'm unable to pair my mibuds using KDE wizard. It always fail.


STEPS TO REPRODUCE
1. Put headphone into pairing state
2. Select MiBuds on wizard
3. Wait

OBSERVED RESULT
Pairing fail

EXPECTED RESULT
Pairing succeed

SOFTWARE/OS VERSIONS
Operating System: Nobara Linux 39
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.6-201.fsync.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6750 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7A37
System Version: 1.0

ADDITIONAL INFORMATION
I can only pair them through bluetoothctl when I set both pairable and discoverable to on
Other than that `pair` command would fail as well

The same bug is also reproducible on arch
Comment 1 TraceyC 2025-01-14 01:36:11 UTC
I'm sorry we weren't able to get to this bug yet. If this is still a problem on your system, can you try pairing your device through command line with bluetoothctl? This will let us know if there's an underlying system problem.

Instructions to connect using bluetoothctl:
1. `sudo systemctl restart bluetooth`
2. `bluetoothctl`
3. `scan on`
4. Write down the MAC for the device: `[bluetooth]# [NEW] Device 88:C9:XXXXXX Device-name
5. `connect <MAC>`
6. `quit`

Please reply with your results. Thanks.
Comment 2 Marcelo Bossoni 2025-01-14 23:14:01 UTC
Created attachment 177361 [details]
bluetoothctl logs
Comment 3 Marcelo Bossoni 2025-01-14 23:20:34 UTC
Created attachment 177362 [details]
logs with connect call only
Comment 4 TraceyC 2025-01-15 15:47:50 UTC
Thanks for your reply and the logs.

From this part of the logs, bluetoothctl sees the mi buds, correctly identifies them, pairs, they are set to trusted and connection is successful. The problem lies in the Bluetooth wizard. I'll let someone more knowledgeable about Bluetooth code take it from here.

[bluetooth]# connect 9C:19:C2:3F:C9:15[CHG] Device 69:2E:19:66:7C:8B ManufacturerData.Key: 0x004c (76)
[bluetooth]# connect 9C:19:C2:3F:C9:15[CHG] Device 69:2E:19:66:7C:8B ManufacturerData.Value:
[bluetooth]# connect 9C:19:C2:3F:C9:15  01 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00  ................
[bluetooth]# connect 9C:19:C2:3F:C9:15  00                                               .               
[bluetooth]# connect 9C:19:C2:3F:C9:15[CHG] Device D4:8D:26:B4:C1:0D RSSI: 0xffffffb0 (-80)
[bluetooth]# connect 9C:19:C2:3F:C9:15
Attempting to connect to 9C:19:C2:3F:C9:15
[Mi True Wireless EBs Basic 2]# [CHG] Device 9C:19:C2:3F:C9:15 Connected: yes
[Mi True Wireless EBs Basic 2]# [CHG] Device 9C:19:C2:3F:C9:15 Modalias: bluetooth:v005Dp223Bd0100
[Mi True Wireless EBs Basic 2]# [CHG] Device 9C:19:C2:3F:C9:15 ServicesResolved: yes
[Mi True Wireless EBs Basic 2]# [CHG] Device 69:2E:19:66:7C:8B ManufacturerData.Key: 0x004c (76)
[Mi True Wireless EBs Basic 2]# [CHG] Device 69:2E:19:66:7C:8B ManufacturerData.Value:
[Mi True Wireless EBs Basic 2]#   01 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00  ................
[Mi True Wireless EBs Basic 2]#   00                                               .               
[Mi True Wireless EBs Basic 2]# [CHG] Device 9C:19:C2:3F:C9:15 Bonded: yes
[Mi True Wireless EBs Basic 2]# [CHG] Device 9C:19:C2:3F:C9:15 Paired: yes
[Mi True Wireless EBs Basic 2]# [CHG] Device 69:2E:19:66:7C:8B ManufacturerData.Key: 0x004c (76)
[Mi True Wireless EBs Basic 2]# [CHG] Device 69:2E:19:66:7C:8B ManufacturerData.Value:
[Mi True Wireless EBs Basic 2]#   01 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00  ................
[Mi True Wireless EBs Basic 2]#   00                                               .               
[Mi True Wireless EBs Basic 2]# [NEW] Endpoint /org/bluez/hci0/dev_9C_19_C2_3F_C9_15/sep1 
[Mi True Wireless EBs Basic 2]# [NEW] Transport /org/bluez/hci0/dev_9C_19_C2_3F_C9_15/sep1/fd3 
[Mi True Wireless EBs Basic 2]# [CHG] Device 69:2E:19:66:7C:8B ManufacturerData.Key: 0x004c (76)
[Mi True Wireless EBs Basic 2]# [CHG] Device 69:2E:19:66:7C:8B ManufacturerData.Value:
[Mi True Wireless EBs Basic 2]#   10 05 33 18 42 ed ea                             ..3.B..         
[Mi True Wireless EBs Basic 2]# Connection successful
Comment 5 Nate Graham 2025-05-09 17:35:27 UTC
Is it still happening with Plasma 6.3 or newer, and also a newer kernel?
Comment 6 Marcelo Bossoni 2025-05-24 19:49:50 UTC
Retested with Plasma 6.4 beta and is unable to reproduce it
Comment 7 TraceyC 2025-05-27 17:26:35 UTC
That's good news. Thanks for letting us know.