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.
Popped-out window (SUPER+O) loses centering when moved to another monitor
Reported by Eidan78 · filed Aug 16, 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
Summary
On a multi-monitor setup, a window popped out with SUPER + O ("Pop window out (float & pin)") is centered on its current monitor, but when the window is moved to another monitor it is not re-centered: it keeps its offset relative to the origin of the monitor it was on.
Expected behavior
The popped-out window should stay centered on the monitor it ends up on, so it remains centered after being moved between monitors (the feature's whole point is a window that "stays fixed" while floating).
Actual behavior
The window lands off-center on the target monitor, retaining its old offset.
Steps to reproduce
- Have two monitors (in my case three: a portrait 2560x1440, a 3840x2160 TV and a rotated 2560x1440).
- Focus a window and press
SUPER + O(pop out: float + pin + center). - Move the window to a workspace on another monitor, e.g. with the "Move window to workspace N" binding (
SUPER+SHIFT+N) or "Move window silently" (SUPER+SHIFT+ALT+N). - The window is not centered on the new monitor.
Example observed positions (window size 1300x900):
- HDMI-A-1 at
10240,4704, popped window centered at11510,5352(offset1270,648from monitor origin). - After moving to workspace 3 on DP-1 (at
14080,4992): window at15350,5640— the same offset1270,648, instead of the monitor center.
Root cause
omarchy-hyprland-window-pop centers the window only once, at pop time (centerwindow). When a floating window is later moved to another monitor, Hyprland preserves its global coordinates (offset from the old monitor origin) and does not re-center it. So the pop-out only stays centered on the monitor where it was created.
Environment
- Omarchy: 4.0.0-1
- Hyprland: 0.56.2 (v0.56.2, commit efb50993780079460b0cbed1363e2166a2de1d9f)
- Kernel: 7.1.8-arch1-3
- GPU: NVIDIA GeForce RTX 3080 Mobile / Max-Q
- Monitors: Dell U2715H (DP-1, portrait), LG TV (HDMI-A-1, 3840x2160), LG ULTRAGEAR (DP-3, rotated)
Suggested fix
Re-center popped-out windows whenever they change monitor — e.g. a small event watcher on the Hyprland socket (movewindow / moveworkspace events) that dispatches centerwindow for windows tagged pop whose monitor changed, or hooking this into omarchy-hyprland-window-pop.
As a local workaround I run a small daemon (~/.local/bin/omarchy-hyprland-pop-recenter) that listens for movewindow/moveworkspace events and re-centers tagged pop windows on their new monitor.
View raw text
## Summary
On a multi-monitor setup, a window popped out with **SUPER + O** ("Pop window out (float & pin)") is centered on its current monitor, but when the window is moved to another monitor it is **not re-centered**: it keeps its offset relative to the origin of the monitor it was on.
## Expected behavior
The popped-out window should stay centered on the monitor it ends up on, so it remains centered after being moved between monitors (the feature's whole point is a window that "stays fixed" while floating).
## Actual behavior
The window lands off-center on the target monitor, retaining its old offset.
## Steps to reproduce
1. Have two monitors (in my case three: a portrait 2560x1440, a 3840x2160 TV and a rotated 2560x1440).
2. Focus a window and press `SUPER + O` (pop out: float + pin + center).
3. Move the window to a workspace on another monitor, e.g. with the "Move window to workspace N" binding (`SUPER+SHIFT+N`) or "Move window silently" (`SUPER+SHIFT+ALT+N`).
4. The window is not centered on the new monitor.
Example observed positions (window size 1300x900):
- HDMI-A-1 at `10240,4704`, popped window centered at `11510,5352` (offset `1270,648` from monitor origin).
- After moving to workspace 3 on DP-1 (at `14080,4992`): window at `15350,5640` — the **same offset** `1270,648`, instead of the monitor center.
## Root cause
`omarchy-hyprland-window-pop` centers the window only once, at pop time (`centerwindow`). When a floating window is later moved to another monitor, Hyprland preserves its global coordinates (offset from the old monitor origin) and does not re-center it. So the pop-out only stays centered on the monitor where it was created.
## Environment
- Omarchy: 4.0.0-1
- Hyprland: 0.56.2 (v0.56.2, commit efb50993780079460b0cbed1363e2166a2de1d9f)
- Kernel: 7.1.8-arch1-3
- GPU: NVIDIA GeForce RTX 3080 Mobile / Max-Q
- Monitors: Dell U2715H (DP-1, portrait), LG TV (HDMI-A-1, 3840x2160), LG ULTRAGEAR (DP-3, rotated)
## Suggested fix
Re-center popped-out windows whenever they change monitor — e.g. a small event watcher on the Hyprland socket (`movewindow` / `moveworkspace` events) that dispatches `centerwindow` for windows tagged `pop` whose monitor changed, or hooking this into `omarchy-hyprland-window-pop`.
As a local workaround I run a small daemon (`~/.local/bin/omarchy-hyprland-pop-recenter`) that listens for `movewindow`/`moveworkspace` events and re-centers tagged `pop` windows on their new monitor.
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 04:27 UTC