Proof Portal

Project overview

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-4419GitHub issuePublicReceived

Missing migration: helpers.lua not loaded in existing hyprland.lua after update

Reported by luizo · filed May 19, 2026Closed upstream on 2026-05-20 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

Missing migration: helpers.lua not loaded in existing hyprland.lua after updaterevision 1 · captured 2026-10-04 11:56 UTC via poll

Problem

After running omarchy update, users with an existing ~/.config/hypr/hyprland.lua get a persistent error banner with multiple config errors like:

require("default.hypr.autostart"): .../default/hypr/autostart.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.bindings.media"): .../default/hypr/bindings/media.lua:2: attempt to index a nil value (global 'o')
require("default.hypr.bindings.clipboard"): .../default/hypr/bindings/clipboard.lua:13: attempt to index a nil value (global 'o')
require("default.hypr.bindings.tiling-v2"): .../default/hypr/bindings/tiling-v2.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.bindings.utilities"): .../default/hypr/bindings/utilities.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.windows"): .../default/hypr/windows.lua:3: attempt to index a nil value (global 'o')

Root Cause

Commit 97d4e908 ("Use the helpers where applicable") updated many default Lua modules to use the o global defined in helpers.lua. The new default/hypr/omarchy.lua correctly loads helpers first:

require("default.hypr.helpers")  -- defines 'o'
require("default.hypr.autostart")
-- ...

However, existing users' `~/.config/hypr/hyprland.lua` was generated before this change and does not include require("default.hypr.helpers"). Since omarchy update never modifies files under ~/.config/ (by design), those users are left with a broken config.

Fix

Manual workaround: Add require("default.hypr.helpers") to ~/.config/hypr/hyprland.lua before the other default requires:

local paths = require("default.hypr.paths")

require("default.hypr.helpers")  -- add this line

require("default.hypr.autostart")
-- ...

Proper fix: A migration script that adds this line automatically, similar to how other migrations in migrations/ update user configs.

Alternatively, the individual modules (autostart.lua, windows.lua, etc.) could guard against a missing o global with a local require("default.hypr.helpers") at the top, making them self-contained and order-independent.

View raw text
## Problem

After running `omarchy update`, users with an existing `~/.config/hypr/hyprland.lua` get a persistent error banner with multiple config errors like:

```
require("default.hypr.autostart"): .../default/hypr/autostart.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.bindings.media"): .../default/hypr/bindings/media.lua:2: attempt to index a nil value (global 'o')
require("default.hypr.bindings.clipboard"): .../default/hypr/bindings/clipboard.lua:13: attempt to index a nil value (global 'o')
require("default.hypr.bindings.tiling-v2"): .../default/hypr/bindings/tiling-v2.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.bindings.utilities"): .../default/hypr/bindings/utilities.lua:1: attempt to index a nil value (global 'o')
require("default.hypr.windows"): .../default/hypr/windows.lua:3: attempt to index a nil value (global 'o')
```

## Root Cause

Commit `97d4e908` ("Use the helpers where applicable") updated many default Lua modules to use the `o` global defined in `helpers.lua`. The new `default/hypr/omarchy.lua` correctly loads helpers first:

```lua
require("default.hypr.helpers")  -- defines 'o'
require("default.hypr.autostart")
-- ...
```

However, **existing users' `~/.config/hypr/hyprland.lua`** was generated before this change and does not include `require("default.hypr.helpers")`. Since `omarchy update` never modifies files under `~/.config/` (by design), those users are left with a broken config.

## Fix

**Manual workaround:** Add `require("default.hypr.helpers")` to `~/.config/hypr/hyprland.lua` before the other default requires:

```lua
local paths = require("default.hypr.paths")

require("default.hypr.helpers")  -- add this line

require("default.hypr.autostart")
-- ...
```

**Proper fix:** A migration script that adds this line automatically, similar to how other migrations in `migrations/` update user configs.

Alternatively, the individual modules (`autostart.lua`, `windows.lua`, etc.) could guard against a missing `o` global with a local `require("default.hypr.helpers")` at the top, making them self-contained and order-independent.

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.

No decision has been recorded yet.