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.
Existing ~/.config/hypr/hyprland.lua not migrated to load default.hypr.helpers after 4.0 update — attempt to index a nil value (global 'o')
Reported by Cyrus-n8n · filed May 16, 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
What happened
After updating omarchy (Hyprland 0.55.2, omarchy 4.0.0.alpha), hyprctl configerrors reports a cascade of Lua errors:
require("default.hypr.autostart"): .../default/hypr/autostart.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.bindings.media"): .../media.lua:2: attempt to index a nil value (global 'o')
require("default.hypr.bindings.clipboard"): .../clipboard.lua:13: attempt to index a nil value (global 'o')
require("default.hypr.bindings.tiling-v2"): .../tiling-v2.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.bindings.utilities"): .../utilities.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.windows"): .../windows.lua:3: attempt to index a nil value (global 'o')As a side effect, none of the autostart processes are launched (waybar, swaybg, hypridle, fcitx5, polkit agent, omarchy-hyprland-monitor-watch) — black screen on login with the red "Your config has errors" banner.
Root cause
default/hypr/helpers.lua defines the global o used by every other default module. The new stock entrypoint default/hypr/omarchy.lua requires it on line 3:
require("default.hypr.helpers")But my pre-existing ~/.config/hypr/hyprland.lua (created on an earlier omarchy version) does not require helpers — and the 4.0 update did not ship a migration that backfills the line. So every subsequent require("default.hypr.*") blows up because o is nil.
The fix in my case was one line:
local paths = require("default.hypr.paths")
+require("default.hypr.helpers")
-- Use Omarchy defaults, but don't edit these directly.
require("default.hypr.autostart")After that, hyprctl reload runs clean and autostart fires normally on next login.
Suggested fix
Add a migration that, for users whose ~/.config/hypr/hyprland.lua requires any default.hypr.* module but does not require default.hypr.helpers, inserts the line right after require("default.hypr.paths") (or at the top of the defaults block).
System
- omarchy: 4.0.0.alpha
- Hyprland: 0.55.2
- Arch (CachyOS) — surfaced immediately after
omarchy update
View raw text
## What happened
After updating omarchy (Hyprland 0.55.2, omarchy 4.0.0.alpha), `hyprctl configerrors` reports a cascade of Lua errors:
```
require("default.hypr.autostart"): .../default/hypr/autostart.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.bindings.media"): .../media.lua:2: attempt to index a nil value (global 'o')
require("default.hypr.bindings.clipboard"): .../clipboard.lua:13: attempt to index a nil value (global 'o')
require("default.hypr.bindings.tiling-v2"): .../tiling-v2.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.bindings.utilities"): .../utilities.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.windows"): .../windows.lua:3: attempt to index a nil value (global 'o')
```
As a side effect, none of the autostart processes are launched (waybar, swaybg, hypridle, fcitx5, polkit agent, omarchy-hyprland-monitor-watch) — black screen on login with the red "Your config has errors" banner.
## Root cause
`default/hypr/helpers.lua` defines the global `o` used by every other default module. The new stock entrypoint `default/hypr/omarchy.lua` requires it on line 3:
```lua
require("default.hypr.helpers")
```
But my pre-existing `~/.config/hypr/hyprland.lua` (created on an earlier omarchy version) does not require helpers — and the 4.0 update did not ship a migration that backfills the line. So every subsequent `require("default.hypr.*")` blows up because `o` is nil.
The fix in my case was one line:
```diff
local paths = require("default.hypr.paths")
+require("default.hypr.helpers")
-- Use Omarchy defaults, but don't edit these directly.
require("default.hypr.autostart")
```
After that, `hyprctl reload` runs clean and autostart fires normally on next login.
## Suggested fix
Add a migration that, for users whose `~/.config/hypr/hyprland.lua` requires any `default.hypr.*` module but does not require `default.hypr.helpers`, inserts the line right after `require("default.hypr.paths")` (or at the top of the defaults block).
## System
- omarchy: 4.0.0.alpha
- Hyprland: 0.55.2
- Arch (CachyOS) — surfaced immediately after `omarchy update`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 03:48 UTC