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.
Lock → unlock leaves Nvidia/DP monitor stuck at 640x480 until power cycle
Reported by thacer13 · filed Sep 7, 2026 · open at source
This defect is tracked under R-323. This report describes the same defect, so it is folded under it in the inbox.
Earliest report of this defect: R-883 (filed Sep 7, 2026).
Decided by agents · verified· Oct 9, 2026
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?
- 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
System details
Acer KG241Q P, DP-1, NVIDIA GeForce GTX 1050
What's wrong?
Environment
- Omarchy 4.0.2-1, Hyprland 0.56.2 (v0.56.2, commit efb50993)
- GPU: NVIDIA GeForce GTX 1050, proprietary driver 580.178.04
- Monitor: Acer KG241Q P, DP-1, native 1920x1080@144, user config pins
hl.monitor({ output = "DP-1", mode = "1920x1080@144", position = "auto", scale = 1.25 })
- No deep-sleep / DP power-saving option in the monitor OSD
What happens
- Lock the machine (
omarchy system lock, or idle timeout).
Lock blanks the display via omarchy-brightness-display off.
2. The Acer drops the DisplayPort link; the GPU loses the EDID.
3. Unlock. Brightness is restored (omarchy-system-wake), but nothing
re-probes the output. hyprctl monitors shows:
Monitor DP-1: [email protected], description: Nvidia 0x0000,
availableModes: [email protected] only.
4. Stuck at 640x480. hyprctl reload does NOT recover (EDID still
unreadable). Only a physical monitor power-cycle restores 1080p144,
which the pinned monitors.lua rule then applies immediately.
Minimal repro (no lock needed)
omarchy-brightness-display off; sleep 6; omarchy-brightness-display on
hyprctl monitors # DP-1 at 640x480, make/model "Nvidia 0x0000"Quickshell lock logs at the time show the output vanishing:Not creating lock surface ... as it is not backed by a valid wayland output,Got removal for monitor "FALLBACK" which was not previously tracked.
Expected
On wake/unlock, re-probe the output and re-apply the configured mode once
the EDID is readable again (or retry the pinned mode instead of settling
on the 640x480 fallback).
Notes
video=DP-1:...kernel param is not applicable (proprietary Nvidia
driver ignores it for Wayland modesetting).
- No user-facing DPMS/idle-display control exists in shell.json
(only idle.screensaver / idle.lock timeouts), and there is no
unlock hook event in ~/.config/omarchy/hooks/, so users cannot
work around this from supported config.
View raw text
### System details
Acer KG241Q P, DP-1, NVIDIA GeForce GTX 1050
### What's wrong?
## Environment
- Omarchy 4.0.2-1, Hyprland 0.56.2 (v0.56.2, commit efb50993)
- GPU: NVIDIA GeForce GTX 1050, proprietary driver 580.178.04
- Monitor: Acer KG241Q P, DP-1, native 1920x1080@144, user config pins
`hl.monitor({ output = "DP-1", mode = "1920x1080@144", position = "auto", scale = 1.25 })`
- No deep-sleep / DP power-saving option in the monitor OSD
## What happens
1. Lock the machine (`omarchy system lock`, or idle timeout).
Lock blanks the display via `omarchy-brightness-display off`.
2. The Acer drops the DisplayPort link; the GPU loses the EDID.
3. Unlock. Brightness is restored (`omarchy-system-wake`), but nothing
re-probes the output. `hyprctl monitors` shows:
`Monitor DP-1: [email protected], description: Nvidia 0x0000`,
`availableModes: [email protected]` only.
4. Stuck at 640x480. `hyprctl reload` does NOT recover (EDID still
unreadable). Only a physical monitor power-cycle restores 1080p144,
which the pinned `monitors.lua` rule then applies immediately.
## Minimal repro (no lock needed)
```bash
omarchy-brightness-display off; sleep 6; omarchy-brightness-display on
hyprctl monitors # DP-1 at 640x480, make/model "Nvidia 0x0000"
```
Quickshell lock logs at the time show the output vanishing:
`Not creating lock surface ... as it is not backed by a valid wayland output`,
`Got removal for monitor "FALLBACK" which was not previously tracked`.
## Expected
On wake/unlock, re-probe the output and re-apply the configured mode once
the EDID is readable again (or retry the pinned mode instead of settling
on the 640x480 fallback).
## Notes
- `video=DP-1:...` kernel param is not applicable (proprietary Nvidia
driver ignores it for Wayland modesetting).
- No user-facing DPMS/idle-display control exists in `shell.json`
(only `idle.screensaver` / `idle.lock` timeouts), and there is no
unlock hook event in `~/.config/omarchy/hooks/`, so users cannot
work around this from supported config.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
- Duplicate ofR-323Don't DPMS-off Apple Studio Display on lock — USB4 tunnel dies until power cycle· decided by agents · verified
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.