Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-1455GitHub issuePublicDecided· Out of scope

Bluetooth keyboards and mice do not work on SDDM login screen

Reported by rodrigojacarei · filed Aug 25, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Bluetooth keyboards and mice do not work on SDDM login screenrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

Intel Core i7-7500U, Intel HD Graphics 620, Realtek RTL8852BE, Omarchy 4.0.1-1

What's wrong?

When booting into the SDDM login screen (or when logged out), paired and trusted Bluetooth input devices (such as a Bluetooth keyboard or mouse) do not work. Because the Bluetooth keyboard cannot connect at the login screen, users cannot type their password to log in without attaching a physical USB keyboard.

Steps to reproduce:

  1. Pair and trust a Bluetooth keyboard (e.g., bluetoothctl trust <MAC>).
  2. Reboot the system to the SDDM login screen (or log out).
  3. Attempt to type the password using the Bluetooth keyboard.
  4. Keystrokes are not received because the device is unable to connect at the greeter.

Root Cause / Analysis:

  • In /usr/share/omarchy/install/hardware/bluetooth.sh, AutoEnable in /etc/bluetooth/main.conf is commented out based on the assumption that BlueZ powers on adapters automatically; however, upstream BlueZ leaves the adapter unpowered unless explicitly configured.
  • sddm.service starts concurrently with bluetooth.service without an After=bluetooth.service ordering constraint.
  • Fast connectable mode (FastConnectable=true) and BLE HID reconnect handling (ReconnectUUIDs / UserspaceHID=true) are not enabled by default, preventing sleeping Bluetooth keyboards from establishing a quick connection at the greeter.
View raw text
### System details
Intel Core i7-7500U, Intel HD Graphics 620, Realtek RTL8852BE, Omarchy 4.0.1-1

### What's wrong?
When booting into the SDDM login screen (or when logged out), paired and trusted Bluetooth input devices (such as a Bluetooth keyboard or mouse) do not work. Because the Bluetooth keyboard cannot connect at the login screen, users cannot type their password to log in without attaching a physical USB keyboard.

#### Steps to reproduce:
1. Pair and trust a Bluetooth keyboard (e.g., `bluetoothctl trust <MAC>`).
2. Reboot the system to the SDDM login screen (or log out).
3. Attempt to type the password using the Bluetooth keyboard.
4. Keystrokes are not received because the device is unable to connect at the greeter.

#### Root Cause / Analysis:
- In `/usr/share/omarchy/install/hardware/bluetooth.sh`, `AutoEnable` in `/etc/bluetooth/main.conf` is commented out based on the assumption that BlueZ powers on adapters automatically; however, upstream BlueZ leaves the adapter unpowered unless explicitly configured.
- `sddm.service` starts concurrently with `bluetooth.service` without an `After=bluetooth.service` ordering constraint.
- Fast connectable mode (`FastConnectable=true`) and BLE HID reconnect handling (`ReconnectUUIDs` / `UserspaceHID=true`) are not enabled by default, preventing sleeping Bluetooth keyboards from establishing a quick connection at the greeter.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 09:08 UTC