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.
hyprland.lua: Sub-module require errors abort script evaluation before hypr.bindings, locking user out of keybindings
Reported by codyoss · filed Sep 2, 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
- Distro: Omarchy 4.x (
quattro) - Compositor: Hyprland 0.56.2 (Lua configuration)
- Affected File:
config/hypr/hyprland.lua
What's wrong?
1. Symptom
If a syntax error, invalid format, or runtime exception occurs inside ~/.config/hypr/monitors.lua (or hypr.input), the graphical desktop still starts (wallpaper and bar render), but none of the user's keyboard shortcuts work (Super + Return for terminal, Super + Space for menu).
The user is stranded on a running desktop with no keyboard control and no way to launch a terminal or text editor to fix their configuration.
2. Root Cause
In config/hypr/hyprland.lua, user override submodules are required linearly using raw require() statements:
-- config/hypr/hyprland.lua (lines 17-21)
require("hypr.monitors")
require("hypr.input")
require("hypr.bindings")
require("hypr.looknfeel")
require("hypr.autostart")Because require("hypr.monitors") runs before require("hypr.bindings"), an unhandled error inside monitors.lua immediately aborts the Lua execution thread. As a result:
1. hypr.bindings is never evaluated.
2. The user loses all emergency recovery hotkeys.
3. Proposed Fix
- Reorder Core Bindings: Ensure
require("hypr.bindings")is loaded before hardware/display configuration overrides. - Defensive Module Loading: Wrap user override submodules in a protected call (
pcall) or a safe loader helper so that a broken monitor/input script logs an error without preventing the rest of the compositor's bindings from loading:
-- Suggested defensive loading pattern in config/hypr/hyprland.lua:
local function safe_require(module)
local ok, err = pcall(require, module)
if not ok then
print("[Omarchy Config Error] Failed to load " .. module .. ": " .. tostring(err))
end
end
-- 1. Load bindings first so the user is never locked out
safe_require("hypr.bindings")
-- 2. Safely load display, input, and visual overrides
safe_require("hypr.monitors")
safe_require("hypr.input")
safe_require("hypr.looknfeel")
safe_require("hypr.autostart")View raw text
### System details
- **Distro:** Omarchy 4.x (`quattro`)
- **Compositor:** Hyprland 0.56.2 (Lua configuration)
- **Affected File:** `config/hypr/hyprland.lua`
### What's wrong?
#### 1. Symptom
If a syntax error, invalid format, or runtime exception occurs inside `~/.config/hypr/monitors.lua` (or `hypr.input`), the graphical desktop still starts (wallpaper and bar render), but **none of the user's keyboard shortcuts work** (`Super + Return` for terminal, `Super + Space` for menu).
The user is stranded on a running desktop with no keyboard control and no way to launch a terminal or text editor to fix their configuration.
#### 2. Root Cause
In `config/hypr/hyprland.lua`, user override submodules are required linearly using raw `require()` statements:
```lua
-- config/hypr/hyprland.lua (lines 17-21)
require("hypr.monitors")
require("hypr.input")
require("hypr.bindings")
require("hypr.looknfeel")
require("hypr.autostart")
```
Because `require("hypr.monitors")` runs **before** `require("hypr.bindings")`, an unhandled error inside `monitors.lua` immediately aborts the Lua execution thread. As a result:
1. `hypr.bindings` is never evaluated.
2. The user loses all emergency recovery hotkeys.
#### 3. Proposed Fix
1. **Reorder Core Bindings:** Ensure `require("hypr.bindings")` is loaded before hardware/display configuration overrides.
2. **Defensive Module Loading:** Wrap user override submodules in a protected call (`pcall`) or a safe loader helper so that a broken monitor/input script logs an error without preventing the rest of the compositor's bindings from loading:
```lua
-- Suggested defensive loading pattern in config/hypr/hyprland.lua:
local function safe_require(module)
local ok, err = pcall(require, module)
if not ok then
print("[Omarchy Config Error] Failed to load " .. module .. ": " .. tostring(err))
end
end
-- 1. Load bindings first so the user is never locked out
safe_require("hypr.bindings")
-- 2. Safely load display, input, and visual overrides
safe_require("hypr.monitors")
safe_require("hypr.input")
safe_require("hypr.looknfeel")
safe_require("hypr.autostart")
```
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 10:32 UTC