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.
omarchy-hyprland-monitor-scaling doesn't persist scale on outputs with explicit per-monitor rules in monitors.lua
Reported by RonRayReed · filed Aug 24, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #6673 (R-1876). GitHub close reason: completed.
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
What happened: On a dual-monitor laptop setup where each display needs a different scale (ultrawide external at scale 1, laptop panel at scale 2), changing the laptop's scale via the monitor panel's SCALE control (or omarchy hyprland monitor scaling <value>) applies briefly, then reverts to the old value within ~2 seconds.
Expected: The chosen scale persists.
Root cause (traced via `~/.local/state/omarchy/monitor-scaling.log`): omarchy-hyprland-monitor-scaling's set_scale() applies the new scale live via hyprctl eval, but only persists it back into monitors.lua when the file matches one of two generic patterns (local omarchy_monitor_scale = ... or the wildcard hl.monitor({ output = "", ... })). When monitors.lua instead has explicit per-output rules (hl.monitor({ output = "eDP-1", ..., scale = X }) — necessary here since the two monitors need different scales), the sed-based persistence silently no-ops. Meanwhile omarchy-hyprland-monitor-watch's docked-mode poller (poll_clamshell_state, active whenever a laptop has an external monitor active) calls omarchy-hyprland-monitor-clamshell every ~2s, which reads the explicit rule's scale from monitors.lua as the desired-state and force-reapplies it — reverting the unpersisted live change.
Steps to reproduce:
1. Connect a laptop to an external monitor with a different native scale need (extended, not mirrored).
2. Set explicit per-output hl.monitor({...}) rules in monitors.lua for both outputs (e.g. via nwg-displays, or by hand).
3. Use the monitor panel's SCALE control (or omarchy hyprland monitor scaling <value>) to change the laptop's scale to a different value.
4. Within ~2 seconds, it reverts to the value still written in monitors.lua.
System: Omarchy 4.0.0-1, Dell Latitude 7420, Hyprland 0.56.2, dual monitor (LG Ultrawide DP-2 + internal eDP-1).
Workaround: Edit monitors.lua's explicit rule directly and reload — this is stable since it removes the live/config mismatch the poller reacts to.
Related: https://discord.com/channels/1390012484194275541/1531291452720550081 — that thread covers a different but adjacent bug in the same two scripts (a Lua-variable scale reference resolving incorrectly on the read side, since fixed). This report is the mirror-image gap on the write/persist side, which isn't fully diagnosed there — Bitslix's Aug 17 comment ("no setting is saved when using gui tools to update the scale") looks like the same symptom, unconfirmed.
Claude Code assisted in both troubleshooting this issue and drafting this report.
View raw text
**What happened:** On a dual-monitor laptop setup where each display needs a different scale (ultrawide external at scale 1, laptop panel at scale 2), changing the laptop's scale via the monitor panel's SCALE control (or `omarchy hyprland monitor scaling <value>`) applies briefly, then reverts to the old value within ~2 seconds.
**Expected:** The chosen scale persists.
**Root cause (traced via `~/.local/state/omarchy/monitor-scaling.log`):** `omarchy-hyprland-monitor-scaling`'s `set_scale()` applies the new scale live via `hyprctl eval`, but only persists it back into `monitors.lua` when the file matches one of two generic patterns (`local omarchy_monitor_scale = ...` or the wildcard `hl.monitor({ output = "", ... })`). When `monitors.lua` instead has explicit per-output rules (`hl.monitor({ output = "eDP-1", ..., scale = X })` — necessary here since the two monitors need different scales), the sed-based persistence silently no-ops. Meanwhile `omarchy-hyprland-monitor-watch`'s docked-mode poller (`poll_clamshell_state`, active whenever a laptop has an external monitor active) calls `omarchy-hyprland-monitor-clamshell` every ~2s, which reads the *explicit* rule's scale from `monitors.lua` as the desired-state and force-reapplies it — reverting the unpersisted live change.
**Steps to reproduce:**
1. Connect a laptop to an external monitor with a different native scale need (extended, not mirrored).
2. Set explicit per-output `hl.monitor({...})` rules in `monitors.lua` for both outputs (e.g. via `nwg-displays`, or by hand).
3. Use the monitor panel's SCALE control (or `omarchy hyprland monitor scaling <value>`) to change the laptop's scale to a different value.
4. Within ~2 seconds, it reverts to the value still written in `monitors.lua`.
**System:** Omarchy 4.0.0-1, Dell Latitude 7420, Hyprland 0.56.2, dual monitor (LG Ultrawide `DP-2` + internal `eDP-1`).
**Workaround:** Edit `monitors.lua`'s explicit rule directly and reload — this is stable since it removes the live/config mismatch the poller reacts to.
**Related:** https://discord.com/channels/1390012484194275541/1531291452720550081 — that thread covers a different but adjacent bug in the same two scripts (a Lua-variable scale reference resolving incorrectly on the *read* side, since fixed). This report is the mirror-image gap on the *write/persist* side, which isn't fully diagnosed there — Bitslix's Aug 17 comment ("no setting is saved when using gui tools to update the scale") looks like the same symptom, unconfirmed.
---
*Claude Code assisted in both troubleshooting this issue and drafting this report.*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
- Fixed bypr/8982· confirmed
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.