OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
audio-input medium very-common DISPUTE

Make Bluetooth devices reconnect on their own after suspend

omarchyarchendeavouroscachyosmanjarohyprlandwaylandbluetoothlaptopdesktop
AUDITED Audited against its sources and confirmed accurate.

Symptom

Bluetooth headphones/keyboard/mouse pair fine but never reconnect on their own. After a suspend/resume, or after the device sleeps, you have to open the Bluetooth panel and connect manually every time. The journal shows bluetoothd[487]: Authentication attempt without agent and bluetoothd[487]: Access denied: org.bluez.Error.Rejected.

Cause

The device is paired but not marked *trusted*. Without the trusted flag BlueZ requires an authorisation agent to be present for each incoming connection. On a bare Hyprland session none is running at that moment, so the reconnect is rejected.

Fix


bluetoothctl

[bluetooth]# devices
[bluetooth]# trust XX:XX:XX:XX:XX:XX
[bluetooth]# connect XX:XX:XX:XX:XX:XX
[bluetooth]# quit

Or non-interactively:


bluetoothctl trust XX:XX:XX:XX:XX:XX

If reconnect still fails and the device was previously paired with Windows on the same machine (dual boot), the device is storing one link key per MAC and yours was overwritten. You must re-pair, and to have it work in both OSes you have to copy the link keys between them (see the Arch Wiki "Dual boot pairing" section).

If the device connects and then drops after a few seconds, with bluetoothd: connect error: Connection refused (111) in the journal, you may be hitting the BlueZ 5.83+ regression affecting multipoint devices. The interim workaround is:


sudo systemctl restart bluetooth.service

Verify

bluetoothctl info XX:XX:XX:XX:XX:XX shows Trusted: yes, and the device reconnects on its own after systemctl suspend and resume.

Sources

bluetooth-not-reconnecting-after-suspend