Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Keyboard backlight not restored on wake/unlock
Reported by burninc0de · filed Aug 20, 2026Closed upstream on 2026-08-21 by its own reporter burninc0de. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
On laptops with software-controlled keyboard backlights (e.g. ASUS via brightnessctl), the keyboard stays dark after lockscreen blanks. Hard to log back in when you cant see what you are typing at night.
The lockscreen blank flow calls omarchy-brightness-keyboard off in blankProcess to turn off the backlight when the screen blanks. But wakeProcess never calls omarchy-brightness-keyboard restore to bring it back after unlock.
This does not affect firmware-controlled backlights — only software-controlled ones where brightnessctl manages the brightness.
Suggested fix — add omarchy-brightness-keyboard restore to the wake command in shell/plugins/lock/Service.qml:
command: ["bash", "-c", "omarchy-brightness-keyboard restore; omarchy-brightness-display on"]This is a no-op on systems where keyboard brightness is hardware-controlled — the brightnessctl call in omarchy-brightness-keyboard fails silently, so it won't affect desktops or keyboards that handle this themselves.
EDIT: reworded for clarity/accuracy
View raw text
On laptops with software-controlled keyboard backlights (e.g. ASUS via `brightnessctl`), the keyboard stays dark after lockscreen blanks. Hard to log back in when you cant see what you are typing at night. The lockscreen blank flow calls `omarchy-brightness-keyboard off` in `blankProcess` to turn off the backlight when the screen blanks. But `wakeProcess` never calls `omarchy-brightness-keyboard restore` to bring it back after unlock. This does **not** affect firmware-controlled backlights — only software-controlled ones where `brightnessctl` manages the brightness. Suggested fix — add `omarchy-brightness-keyboard restore` to the wake command in `shell/plugins/lock/Service.qml`: ```qml command: ["bash", "-c", "omarchy-brightness-keyboard restore; omarchy-brightness-display on"] ``` This is a no-op on systems where keyboard brightness is hardware-controlled — the `brightnessctl` call in `omarchy-brightness-keyboard` fails silently, so it won't affect desktops or keyboards that handle this themselves. EDIT: reworded for clarity/accuracy
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.
No decision has been recorded yet.