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.
Кeyboard backlight dies before lock screen after resume (ASUS)
Reported by PraiseTheDuck · filed Aug 19, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6667 (R-1877). GitHub close reason: completed.
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
System details
ASUS G16 (2025), Omarchy 4.0.0 (asus::kbd_backlight, max=3)
What's wrong?
After resume the backlight is on. Just before the lock screen appears, shell/plugins/lock/Service.qml calls omarchy-brightness-keyboard off and the lights stay off.
My guess: two control paths that don’t talk to each other:
- omarchy-brightness-keyboard → brightnessctl/sysfs;
- omarchy-theme-set-keyboard-asus-rog → asusctl aura effect static.
After the theme command the lights are on, but sysfs still reads 0. So restore/up/down see 0% and the OSD is wrong.
Expected: either don’t turn keyboard backlight off on lock, or restore must actually bring the previous state back (via asusctl on ASUS).
View raw text
### System details ASUS G16 (2025), Omarchy 4.0.0 (asus::kbd_backlight, max=3) ### What's wrong? After resume the backlight is on. Just before the lock screen appears, shell/plugins/lock/Service.qml calls omarchy-brightness-keyboard off and the lights stay off. My guess: two control paths that don’t talk to each other: - omarchy-brightness-keyboard → brightnessctl/sysfs; - omarchy-theme-set-keyboard-asus-rog → asusctl aura effect static. After the theme command the lights are on, but sysfs still reads 0. So restore/up/down see 0% and the OSD is wrong. **Expected:** either don’t turn keyboard backlight off on lock, or restore must actually bring the previous state back (via asusctl on ASUS).
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
- Related PRpr/5839· confirmed
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.