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.
MacBookAir5,1: minimum brightness turns backlight fully off and Fn+F2 cannot recover
Reported by sonique6784 · filed Sep 21, 2026 · open at source
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
System
- MacBook model: MacBookAir5,1
- Omarchy: 4.0.4-1
- Kernel: 7.2.5-3-omarchy
- GPU: Intel Ivy Bridge mobile GT2 / HD Graphics 4000
- Display: eDP-1, Apple Color LCD, 1366x768
- Backlight device: acpi_video0
- Backlight range: 1/15
Steps to reproduce
- Boot into Omarchy on the MacBook Air.
- Press
Fn+F1repeatedly until brightness reaches its minimum. - The display becomes completely black.
- Press
Fn+F2repeatedly.
Expected behavior
The minimum brightness should leave the backlight at a nonzero hardware level, and Fn+F2 should restore brightness.
Actual behavior
The display becomes completely black. Pressing Fn+F2 does not restore it, so the computer cannot be used normally.
The display can be recovered from a TTY or SSH session with:
brightnessctl -d acpi_video0 set 50%Additional details
The MacBook exposes only 15 discrete backlight levels. Omarchy appears to use a minimum of 1%, which may round down to hardware level 0. The likely affected path is the omarchy-brightness-display handling for low-resolution ACPI backlight devices.
The issue was reproduced with the stock Omarchy brightness keybindings; no local Hyprland brightness override is configured.
Diagnostics
omarchy-debug --no-sudo --print was run locally. Relevant results:
Omarchy Package: omarchy 4.0.4-1
Kernel: 7.2.5-3-omarchy
System: Apple MacBookAir5,1
Graphics: Intel Ivy Bridge mobile GT2 / HD Graphics 4000, driver i915
Monitor: eDP-1, Apple Color LCD, 1366x768View raw text
## System - MacBook model: MacBookAir5,1 - Omarchy: 4.0.4-1 - Kernel: 7.2.5-3-omarchy - GPU: Intel Ivy Bridge mobile GT2 / HD Graphics 4000 - Display: eDP-1, Apple Color LCD, 1366x768 - Backlight device: acpi_video0 - Backlight range: 1/15 ## Steps to reproduce 1. Boot into Omarchy on the MacBook Air. 2. Press `Fn+F1` repeatedly until brightness reaches its minimum. 3. The display becomes completely black. 4. Press `Fn+F2` repeatedly. ## Expected behavior The minimum brightness should leave the backlight at a nonzero hardware level, and `Fn+F2` should restore brightness. ## Actual behavior The display becomes completely black. Pressing `Fn+F2` does not restore it, so the computer cannot be used normally. The display can be recovered from a TTY or SSH session with: ```sh brightnessctl -d acpi_video0 set 50% ``` ## Additional details The MacBook exposes only 15 discrete backlight levels. Omarchy appears to use a minimum of `1%`, which may round down to hardware level `0`. The likely affected path is the `omarchy-brightness-display` handling for low-resolution ACPI backlight devices. The issue was reproduced with the stock Omarchy brightness keybindings; no local Hyprland brightness override is configured. ## Diagnostics `omarchy-debug --no-sudo --print` was run locally. Relevant results: ```text Omarchy Package: omarchy 4.0.4-1 Kernel: 7.2.5-3-omarchy System: Apple MacBookAir5,1 Graphics: Intel Ivy Bridge mobile GT2 / HD Graphics 4000, driver i915 Monitor: eDP-1, Apple Color LCD, 1366x768 ```
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 16:57 UTC