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.
Monitor positions don't auto-adjust when scale changes, causing overlap
Reported by gbenselum · filed Sep 23, 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
When changing monitor scale factor in ~/.config/hypr/monitors.lua, hardcoded position values (in logical pixels) cause monitor overlap because Hyprland interprets positions as physical pixels.
Steps to reproduce:
1. Configure two monitors with hardcoded positions (e.g., DP-1 at 0x0, eDP-1 at 0x540)
2. Set scale = 2 for both
3. Reload Hyprland
4. Monitors overlap (~50% in this case)
Expected: Positions should auto-recalculate for physical pixels when scale changes, or Omarchy should provide a helper.
Workaround: Use position = "auto" or manually multiply positions by scale factor.
System: Omarchy 4.0.4-1, Hyprland Hyprland 0.56.2 built from branch v0.56.2 at commit efb50993780079460b0cbed1363e2166a2de1d9f clean ([gha] Nix: update inputs).
Config example showing the issue:
local omarchy_gdk_scale = 2
local omarchy_monitor_scale = 2
hl.env("GDK_SCALE", tostring(omarchy_gdk_scale))
hl.monitor({ output = "DP-1", mode = "1920x1080@60", position = "0x0", scale = omarchy_monitor_scale })
hl.monitor({ output = "eDP-1", mode = "preferred", position = "0x540", scale = omarchy_monitor_scale })With scale=2:
- DP-1: 1920x1080 → 3840x2160 physical at 0x0
- eDP-1: position 0x540 → 0x1080 physical (540 * 2)
- Result: eDP-1 starts at y=1080, overlapping DP-1's bottom 1080px (50% overlap)
Screenshot attached showing the overlap.
View raw text
When changing monitor scale factor in ~/.config/hypr/monitors.lua, hardcoded position values (in logical pixels) cause monitor overlap because Hyprland interprets positions as physical pixels.
**Steps to reproduce:**
1. Configure two monitors with hardcoded positions (e.g., DP-1 at 0x0, eDP-1 at 0x540)
2. Set scale = 2 for both
3. Reload Hyprland
4. Monitors overlap (~50% in this case)
**Expected:** Positions should auto-recalculate for physical pixels when scale changes, or Omarchy should provide a helper.
**Workaround:** Use `position = "auto"` or manually multiply positions by scale factor.
**System:** Omarchy 4.0.4-1, Hyprland Hyprland 0.56.2 built from branch v0.56.2 at commit efb50993780079460b0cbed1363e2166a2de1d9f clean ([gha] Nix: update inputs).
**Config example showing the issue:**
```lua
local omarchy_gdk_scale = 2
local omarchy_monitor_scale = 2
hl.env("GDK_SCALE", tostring(omarchy_gdk_scale))
hl.monitor({ output = "DP-1", mode = "1920x1080@60", position = "0x0", scale = omarchy_monitor_scale })
hl.monitor({ output = "eDP-1", mode = "preferred", position = "0x540", scale = omarchy_monitor_scale })
```
With scale=2:
- DP-1: 1920x1080 → 3840x2160 physical at 0x0
- eDP-1: position 0x540 → 0x1080 physical (540 * 2)
- Result: eDP-1 starts at y=1080, overlapping DP-1's bottom 1080px (50% overlap)
**Screenshot attached** showing the overlap.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 17:41 UTC