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

Make a paired Bluetooth keyboard work at the SDDM login screen

omarchyarchendeavouroscachyoshyprlandwaylandlaptopdesktop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The problem is real and the SDDM ordering drop-in is appropriate: Omarchy 4.x does use SDDM (install/login/sddm.sh exists upstream), so that half applies. The defect is the first block: tee -a appends a whole new [Policy] section to /etc/bluetooth/main.conf, which already ships one (the sibling AutoEnable record documents [Policy] AutoEnable=false living there). main.conf is parsed as a GKeyFile, and a duplicated group with a conflicting AutoEnable is at best ambiguous and at worst a parse failure that makes bluetoothd fall back to defaults for the whole file. Edit the existing section in place. ReconnectAttempts/ReconnectIntervals are [Policy] keys and FastConnectable is a [General] key, so they cannot all go in one appended block anyway.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

FastConnectable=true keeps the controller in page-scan mode continuously, which increases idle power draw slightly on laptops.

Symptom

A paired and trusted Bluetooth keyboard or mouse does not work at the SDDM greeter or after logging out. You cannot type your password without plugging in a USB keyboard. Once logged in with a wired keyboard, the Bluetooth one connects normally.

Cause

Two things combine. First, AutoEnable is not set in /etc/bluetooth/main.conf, so bluetoothd leaves the adapter unpowered until a user session turns it on. Second, sddm.service starts concurrently with bluetooth.service with no ordering constraint, so the greeter is already up before any adapter exists. Sleeping BLE HID devices also need FastConnectable to reconnect quickly enough for the greeter.

Fix

Edit the existing sections in place instead of appending a second [Policy]:


grep -n -E '^\[|AutoEnable|FastConnectable|ReconnectAttempts|ReconnectIntervals' /etc/bluetooth/main.conf

sudo sed -i \
  -e 's/^[#[:space:]]*AutoEnable[[:space:]]*=.*/AutoEnable=true/' \
  -e 's/^[#[:space:]]*ReconnectAttempts[[:space:]]*=.*/ReconnectAttempts=7/' \
  -e 's/^[#[:space:]]*ReconnectIntervals[[:space:]]*=.*/ReconnectIntervals=1,2,4,8,16,32,64/' \
  -e 's/^[#[:space:]]*FastConnectable[[:space:]]*=.*/FastConnectable=true/' \
  /etc/bluetooth/main.conf

# confirm each landed exactly once, and note which section it is under
grep -n -E '^\[|AutoEnable|FastConnectable|ReconnectAttempts|ReconnectIntervals' /etc/bluetooth/main.conf
sudo systemctl restart bluetooth
systemctl status bluetooth --no-pager    # a parse error here means the file is malformed

If a key is genuinely absent, add it under the correct existing header. AutoEnable, ReconnectAttempts and ReconnectIntervals go under [Policy], and FastConnectable goes under [General]. Do not append a duplicate section.

The SDDM ordering drop-in and bluetoothctl trust AA:BB:CC:DD:EE:FF steps are correct as written.

Verify

Reboot to the greeter and type on the Bluetooth keyboard. From a TTY (Ctrl+Alt+F2) before logging in, bluetoothctl show | grep Powered prints Powered: yes and bluetoothctl info AA:BB:CC:DD:EE:FF shows Connected: yes.

Sources

bluetooth-keyboard-dead-at-login-screen