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 settings inconsistently jump in steps of 9 or 10
Reported by sockbot · filed Apr 24, 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 details
┌──────────────────────Hardware──────────────────────┐
PC: MacBook Air (11-inch, Mid 2013/Early 2014) (1.0)
│ ├: Intel(R) Core(TM) i5-4260U (4) @ 2.70 GHz
│ ├: Intel Haswell-ULT Integrated Graphics Controller @ 1.00 GHz [Integrated]
│ ├: 1366x768 in 12", 60 Hz [Built-in]
│ ├: 82.81 GiB / 231.74 GiB (36%) - btrfs
│ ├: 2.01 GiB / 3.76 GiB (54%)
└ └ : 424.08 MiB / 1.88 GiB (22%)
└────────────────────────────────────────────────────┘
┌──────────────────────Software──────────────────────┐
OS: Omarchy 3.6.0
│ ├: HEAD
│ ├: stable
│ ├: Linux 6.19.12-arch1-1
│ ├: Hyprland 0.54.3 (Wayland)
│ ├: ghostty 1.3.1-arch2
│ ├: 1188 (pacman)
│ ├: Kanagawa ●●●●●●●●
└ └: JetBrainsMono Nerd Font (9pt)
└────────────────────────────────────────────────────┘What's wrong?
Issue
When increasing keyboard backlight brightness, the levels are set to:
0, 9, 19, 29, 39, 49, 58, 68, 78, 88, 98, 100
When decreasing brightness, the levels are set to:
100, 90, 80, 70, 60, 50, 41, 31, 21, 11, 1, 0
This means in order to set my brightness to 1%, I must first set the brightness to 100, then lower it to 1 without accidentally setting to 0.
Expected behaviour
Keyboard brightness should be set to fixed values that are consistent going up and down. Those fixed values should include 0 (off), 1 (minimal brightness) and 100 (maximum brightness).
Instructions to reproduce
git checkout v3.6.0
Raise and lower keyboard backlight brightness using dedicated keys.
View raw text
### System details ``` ┌──────────────────────Hardware──────────────────────┐ PC: MacBook Air (11-inch, Mid 2013/Early 2014) (1.0) │ ├: Intel(R) Core(TM) i5-4260U (4) @ 2.70 GHz │ ├: Intel Haswell-ULT Integrated Graphics Controller @ 1.00 GHz [Integrated] │ ├: 1366x768 in 12", 60 Hz [Built-in] │ ├: 82.81 GiB / 231.74 GiB (36%) - btrfs │ ├: 2.01 GiB / 3.76 GiB (54%) └ └ : 424.08 MiB / 1.88 GiB (22%) └────────────────────────────────────────────────────┘ ┌──────────────────────Software──────────────────────┐ OS: Omarchy 3.6.0 │ ├: HEAD │ ├: stable │ ├: Linux 6.19.12-arch1-1 │ ├: Hyprland 0.54.3 (Wayland) │ ├: ghostty 1.3.1-arch2 │ ├: 1188 (pacman) │ ├: Kanagawa ●●●●●●●● └ └: JetBrainsMono Nerd Font (9pt) └────────────────────────────────────────────────────┘ ``` ### What's wrong? ### Issue When increasing keyboard backlight brightness, the levels are set to: 0, 9, 19, 29, 39, 49, 58, 68, 78, 88, 98, 100 When decreasing brightness, the levels are set to: 100, 90, 80, 70, 60, 50, 41, 31, 21, 11, 1, 0 This means in order to set my brightness to 1%, I must first set the brightness to 100, then lower it to 1 without accidentally setting to 0. ### Expected behaviour Keyboard brightness should be set to fixed values that are consistent going up and down. Those fixed values should include 0 (off), 1 (minimal brightness) and 100 (maximum brightness). ### Instructions to reproduce `git checkout v3.6.0` Raise and lower keyboard backlight brightness using dedicated keys.
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 02:49 UTC