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.
Config incompatibility with Hyprland 0.55: col.border_locked_* and dwindle.pseudotile
Reported by guscall · filed May 16, 2026Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
Summary
After updating to Hyprland v0.55.1, the default config file \~/.local/share/omarchy/default/hypr/looknfeel.conf\ produces three config errors that trigger Hyprland's error overlay at the top of the screen.
Errors
\\\`
Config error in file ~/.local/share/omarchy/default/hypr/looknfeel.conf at line 53: Error parsing gradient -1: failed to parse -1 as a color
Config error in file ~/.local/share/omarchy/default/hypr/looknfeel.conf at line 54: Error parsing gradient -1: failed to parse -1 as a color
Config error in file ~/.local/share/omarchy/default/hypr/looknfeel.conf at line 111: config option <dwindle:pseudotile> does not exist.
\\\`
Root Cause
Two breaking changes in Hyprland 0.55:
- \`-1\` is no longer a valid color/gradient value (lines 53–54):
\\\`ini
col.border_locked_active = -1
col.border_locked_inactive = -1
\\\`
- \`dwindle.pseudotile\` option was removed (line 111):
\\\`ini
dwindle {
pseudotile = true
...
}
\\\`
Fix
\\\`ini
lines 53-54: use the already-defined variables instead of -1
col.border_locked_active = $activeBorderColor
col.border_locked_inactive = $inactiveBorderColor
line 111: remove or comment out pseudotile
pseudotile removed in Hyprland 0.55
\\\`
Environment
- Omarchy: 3.8.1
- Hyprland: 0.55.1
View raw text
## Summary
After updating to Hyprland v0.55.1, the default config file \`~/.local/share/omarchy/default/hypr/looknfeel.conf\` produces three config errors that trigger Hyprland's error overlay at the top of the screen.
## Errors
\`\`\`
Config error in file ~/.local/share/omarchy/default/hypr/looknfeel.conf at line 53: Error parsing gradient -1: failed to parse -1 as a color
Config error in file ~/.local/share/omarchy/default/hypr/looknfeel.conf at line 54: Error parsing gradient -1: failed to parse -1 as a color
Config error in file ~/.local/share/omarchy/default/hypr/looknfeel.conf at line 111: config option <dwindle:pseudotile> does not exist.
\`\`\`
## Root Cause
Two breaking changes in Hyprland 0.55:
1. **\`-1\` is no longer a valid color/gradient value** (lines 53–54):
\`\`\`ini
col.border_locked_active = -1
col.border_locked_inactive = -1
\`\`\`
2. **\`dwindle.pseudotile\` option was removed** (line 111):
\`\`\`ini
dwindle {
pseudotile = true
...
}
\`\`\`
## Fix
\`\`\`ini
# lines 53-54: use the already-defined variables instead of -1
col.border_locked_active = $activeBorderColor
col.border_locked_inactive = $inactiveBorderColor
# line 111: remove or comment out pseudotile
# pseudotile removed in Hyprland 0.55
\`\`\`
## Environment
- Omarchy: 3.8.1
- Hyprland: 0.55.1Validation
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.