Proof Portal

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-1386GitHub issuePublicDecided· Out of scope

omarchy-brightness-display: Brightness trapped at 0% on displays with low max_brightness (acpi_video0)

Reported by gorem · filed Aug 27, 2026 · open at source

Open at source

Decided: Out of scope — decided by agents · verified 5 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

omarchy-brightness-display: Brightness trapped at 0% on displays with low max_brightness (acpi_video0)revision 1 · captured 2026-09-28 21:24 UTC via poll

System details

2012 13" MacBook Pro (Retina)

What's wrong?

Description

On devices where the backlight driver has a low max_brightness value (such as acpi_video0 on a 2012 Retina MacBook Pro, where max_brightness is 15), turning the brightness down to 0% with Fn+F1 locks the backlight at 0%. Pressing Fn+F2 cannot increase the brightness because 1% rounds to raw step 0.

Steps to Reproduce

On a machine using acpi_video0 (max_brightness: 15), press Fn+F1 (XF86MonBrightnessDown) until brightness reaches 0%.
Press Fn+F2 (XF86MonBrightnessUp).

Expected Behavior

Brightness should increase back above 0%.

Actual Behavior

Brightness remains at 0% (screen completely black). The user is locked out and cannot recover without remote shell access or hard rebooting.

Technical Diagnosis

In omarchy-brightness-display:

if [[ $step == "+5%" ]]; then
if (( current < 5 )); then
(( target = current + 1 ))
else
(( target = current + 5 ))
fi
step="$target%"

When current = 0, target becomes 1%.
Executing brightnessctl -d acpi_video0 set 1% calculates 0.01 * 15 = 0.15, which brightnessctl rounds to raw 0. As a result, current stays 0 on every +5% invocation.

Suggested Fix

Ensure omarchy-brightness-display increases raw brightness by at least +1 step when current < 5 or when percentage rounding yields 0.

View raw text

### System details

2012 13" MacBook Pro (Retina)

### What's wrong?

#### Description

On devices where the backlight driver has a low `max_brightness` value (such as `acpi_video0` on a 2012 Retina MacBook Pro, where `max_brightness` is `15`), turning the brightness down to 0% with `Fn+F1` locks the backlight at 0%. Pressing `Fn+F2` cannot increase the brightness because `1%` rounds to raw step 0.

#### Steps to Reproduce

1. On a machine using `acpi_video0` (`max_brightness: 15`), press `Fn+F1` (`XF86MonBrightnessDown`) until brightness reaches 0%.
2. Press `Fn+F2` (`XF86MonBrightnessUp`).

#### Expected Behavior

Brightness should increase back above 0%.

#### Actual Behavior

Brightness remains at 0% (screen completely black). The user is locked out and cannot recover without remote shell access or hard rebooting.

#### Technical Diagnosis

In omarchy-brightness-display:

  if [[ $step == "+5%" ]]; then
    if (( current < 5 )); then
      (( target = current + 1 ))
    else
      (( target = current + 5 ))
    fi
    step="$target%"

When `current = 0`, `target` becomes `1%`.
Executing `brightnessctl -d acpi_video0 set 1%` calculates `0.01 * 15 = 0.15`, which `brightnessctl` rounds to raw `0`. As a result, `current` stays `0` on every `+5%` invocation.

#### Suggested Fix

Ensure `omarchy-brightness-display` increases raw brightness by at least +1 step when `current < 5` or when percentage rounding yields 0.

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:28 UTC

Proof

History & reports

Reference