SUMMARY STEPS TO REPRODUCE 1) Open System Settings > Bluetooth > Devices > "+" (Plus sign to add new device) 2) "MX Keys" device is shown in the "Bluetooth Device Wizzard" windw 3) Click on it and click next 4) "Connecting to MX Keys" progress is show for about 30 seconds 5) "The setup of MX Keys has failed" is shown, with no other info and options to restart the process or close OBSERVED RESULT Keyboard does not connect via bluetooth EXPECTED RESULT Keyboard connects via bluetooth SOFTWARE/OS VERSIONS Linux: Fedora 32 (Kernel: 5.7.7-200) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Any help would be appreciated. I'm not even sure how to debug this since nothing is show when I do `journalctl -f -u bluetooth` nor `dmesg -w`. Keyboard connects fine to an Android device.
A bit further investigation and I found this in the journal logs: bluedevil-wizard[1063770]: org.kde.bluez: PendingCall Error: "In Progress" bluedevil-wizard[1063770]: org.kde.bluez: PendingCall Error: "Operation already in progress" bluedevil-wizard[1063770]: org.kde.bluez: PendingCall Error: "In Progress" bluedevil-wizard[1065035]: org.kde.bluez: PendingCall Error: "Authentication Failed" bluedevil-wizard[1065035]: org.kde.bluez: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." Also, while attempting to pair with bluetoothctl I get this: pair F2:5B:83:FC:F6:EF Attempting to pair with F2:5B:83:FC:F6:EF Failed to pair: org.bluez.Error.AuthenticationCanceled So this seems like it's a issue further down the BT stack probably.
Other times I get "Failed to pair: org.bluez.Error.AuthenticationFailed" from bluetoothctl also.
Hi, it's been a while since you reported. Does the issue still occur to you? And did you use the same Bluetooth adapter in a dual-boot system? I also bought MX Keys keyboard, in 2022, and used it mostly without issues up until about half a year ago (winter 2024). Messages like "Error.AuthenticationFailed" from bluetoothctl is a clear indication of something going south in upstream BlueZ project. Hopefully they fixed it since.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.