Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-946GitHub issuePublicDecided· Out of scope

External monitor reconnect can ignore configured mode in clamshell dock setup

Reported by mkeiji · filed Sep 5, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

External monitor reconnect can ignore configured mode in clamshell dock setuprevision 1 · captured 2026-09-28 21:23 UTC via poll

Problem

On a ThinkPad T480 used in clamshell mode with a dock and two external monitors, an external monitor can reconnect using the wrong mode even though it has an explicit rule in ~/.config/hypr/monitors.lua.

Configured rule:

hl.monitor({ output = "DP-3", mode = "2560x1440@120", position = "0x0", scale = 1 })

The Gigabyte M32U on DP-3 is instead restored as 1920x1080@120 after using the laptop undocked and reconnecting the dock. DP-5 is a Dell U2415.

A manual hyprctl reload or the equivalent hyprctl eval rule restores the configured mode. hyprctl configerrors reports no errors.

Reproduction

  1. Use an Omarchy laptop with the lid closed and a dock connected to two monitors.
  2. Configure an explicit monitor mode in ~/.config/hypr/monitors.lua for DP-3.
  3. Disconnect the dock and use the laptop display.
  4. Reconnect the dock with the lid closed.
  5. Observe that DP-3 may come back at 1920x1080@120 rather than the configured 2560x1440@120.
  6. Run hyprctl reload; the configured mode is restored.

Diagnostics

  • Omarchy: 4.0.2-1
  • Hyprland: 0.56.2
  • Hardware: Lenovo ThinkPad T480, Intel UHD Graphics 620 (i915)
  • DP-3: Gigabyte M32U, modes include 2560x1440@120 and 3840x2160@60
  • DP-5: Dell U2415
  • Internal panel: eDP-1, 1920x1080

The Omarchy monitor scaling log shows monitor operations being initiated by Quickshell, and the current session had two omarchy-hyprland-monitor-watch processes. The suspected area is the monitor hotplug/clamshell watcher: reconnect handling may race EDID/mode probing or fail to reapply user monitor rules after the external output is added.

omarchy debug --no-sudo --print was run locally; no sudo-only data was collected.

View raw text
## Problem

On a ThinkPad T480 used in clamshell mode with a dock and two external monitors, an external monitor can reconnect using the wrong mode even though it has an explicit rule in `~/.config/hypr/monitors.lua`.

Configured rule:

```lua
hl.monitor({ output = "DP-3", mode = "2560x1440@120", position = "0x0", scale = 1 })
```

The Gigabyte M32U on `DP-3` is instead restored as `1920x1080@120` after using the laptop undocked and reconnecting the dock. `DP-5` is a Dell U2415.

A manual `hyprctl reload` or the equivalent `hyprctl eval` rule restores the configured mode. `hyprctl configerrors` reports no errors.

## Reproduction

1. Use an Omarchy laptop with the lid closed and a dock connected to two monitors.
2. Configure an explicit monitor mode in `~/.config/hypr/monitors.lua` for `DP-3`.
3. Disconnect the dock and use the laptop display.
4. Reconnect the dock with the lid closed.
5. Observe that `DP-3` may come back at `1920x1080@120` rather than the configured `2560x1440@120`.
6. Run `hyprctl reload`; the configured mode is restored.

## Diagnostics

- Omarchy: `4.0.2-1`
- Hyprland: `0.56.2`
- Hardware: Lenovo ThinkPad T480, Intel UHD Graphics 620 (`i915`)
- DP-3: Gigabyte M32U, modes include `2560x1440@120` and `3840x2160@60`
- DP-5: Dell U2415
- Internal panel: `eDP-1`, `1920x1080`

The Omarchy monitor scaling log shows monitor operations being initiated by Quickshell, and the current session had two `omarchy-hyprland-monitor-watch` processes. The suspected area is the monitor hotplug/clamshell watcher: reconnect handling may race EDID/mode probing or fail to reapply user monitor rules after the external output is added.

`omarchy debug --no-sudo --print` was run locally; no sudo-only data was collected.

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

  • Related PRpr/7146· 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.

  • Out of scopeDecided by agents · verified · 2026-10-09 10:50 UTC