OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network medium common DISPUTE

Pair a Bluetooth keyboard that needs a displayed passkey

omarchyarchendeavouroscachyoshyprlandwaylandlaptopdesktop
AUDITED Audited against its sources and confirmed accurate.

Symptom

Pairing a Bluetooth keyboard (e.g. Logitech MX Mechanical Mini) from the GUI panel never completes. The panel does not show the six-digit passkey, the device flips repeatedly between "paired" and "connected", and the keyboard never becomes usable. The user journal shows the prompt going to a headless agent instead:


bt-agent[1184]: Authorize this device pairing (yes/no)? Device: MX MCHNCL M (XX:XX:XX:XX:XX:XX)

Cause

The pairing agent that registered with BlueZ does not implement DisplayPasskey/KeyboardDisplay capability, so BlueZ has nowhere to render the six digits the keyboard is waiting for. The pairing negotiation stalls and BlueZ tears it down and retries.

Fix

Pair interactively with an agent that can display the passkey:


# stop the panel/agent from racing you
systemctl --user stop bt-agent.service

bluetoothctl

Then, at the [bluetooth]# prompt:


power on
agent KeyboardDisplay
default-agent
scan on
# put the keyboard into pairing mode, note its MAC when it appears
pair AA:BB:CC:DD:EE:FF
# type the displayed six digits on the Bluetooth keyboard, then press Enter
trust AA:BB:CC:DD:EE:FF
connect AA:BB:CC:DD:EE:FF
scan off
quit

Then restart the agent: systemctl --user start bt-agent.service.

Verify

bluetoothctl info AA:BB:CC:DD:EE:FF shows Paired: yes, Bonded: yes, Trusted: yes, Connected: yes, and the keyboard types.

Sources

bluetooth-passkey-pairing-fails-in-panel