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.
Lid-open resume flickers (lock → dead input → black → lock) from i915 link-training failure at forced 144Hz + forced HDMI rule
Reported by YashasVM · filed Sep 18, 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?
- 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. So far: partly in the audited area (lock) — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.
Original report
Symptom
On an HP Victus 15-fa1xxx (Intel Raptor Lake-P iGPU + NVIDIA RTX 4050 Mobile, BOE eDP panel), closing the lid suspends fine, but opening it does not resume instantly:
1. Lock screen appears, but keyboard (AT Translated Set 2) and touchpad (ELAN0788 on i2c) accept no input for a few seconds.
2. Screen goes black, then the lock screen comes back and input works.
Evidence (local journal, redacted)
Lock itself succeeds fast before suspend, so this is not a lock-service failure:
22:23:17 systemd-logind: Lid closed / Suspending...
22:23:17 omarchy-shell: lock-requested / lock-pending: screen-stabilizing
22:23:17 omarchy-shell: secure=true
22:23:17 systemd-sleep: Performing sleep operation 'suspend' (s2idle)
22:23:44 systemd-logind: Lid opened.
22:23:45 systemd-sleep: System returned from sleep operation 'suspend'.The display driver fails panel link training on resume — and keeps failing afterwards:
i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:508:eDP-1][ENCODER:507:DDI A/PHY A][DPRX] Failed to enable link trainingSeen at 22:23:44 (resume), then again 22:24:01, 22:24:41, 22:26:45 with no further suspends. Also on resume: i915 raw-wakerefs=1 wakelocks=1 on cleanup warning and an nvidia-drm flip-event warning. /sys/power/mem_sleep offers only [s2idle] (no deep S3), kernel 7.2.5-3-omarchy, Hyprland 0.56.2, BIOS F.18.
Related but distinct from #8112 (sleep-lock inhibitor race): that failure line also appears here (Failed to inhibit: already running on the respawned monitor), but the lock had already gone secure, so it does not explain the flicker/dead input.
Likely contributors in Omarchy defaults/user config
~/.config/hypr/monitors.luaforcedeDP-1to1920x1080@144(panel max) and forcedHDMI-A-1to1920x1080@60at a fixed position even with nothing plugged in (hyprctl monitors all -jshows only eDP-1). Every resume therefore does a 144Hz eDP modeset known-flaky with PSR on this iGPU, plus a dead-output probe.- The shell holds the session lock 500ms for screen stabilization (
lock/Service.qmlsessionLockStabilizeTimer), which is correct, but the password field is presented before the i2c input devices finish re-probing, so first-seconds typing goes nowhere.
Local workaround applied (safe, no reboot)
eDP-1→1920x1080@60,HDMI-A-1→mode preferred, position autoso resume is a single clean 60Hz modeset.hyprctl configerrorsclean,hyprctl monitorsconfirms 60Hz. Still to test across several lid cycles; kernel optioni915.enable_psr=0not yet tried (needs Limine cmdline + reboot).
Suggestions for Omarchy
- Do not ship/encourage a forced HDMI rule when no external monitor is connected — prefer
preferred/autoor commented-out, so resume does one eDP modeset. - Consider calling out 144Hz + PSR resume flakiness (or a 60Hz fallback note) for Raptor Lake-P BOE panels.
- Consider gating password-field focus/accept on input-device readiness after resume, or showing a brief 'waking devices…' state, since the lock currently looks ready while i2c input is still down.
View raw text
## Symptom On an HP Victus 15-fa1xxx (Intel Raptor Lake-P iGPU + NVIDIA RTX 4050 Mobile, BOE eDP panel), closing the lid suspends fine, but opening it does not resume instantly: 1. Lock screen appears, but keyboard (AT Translated Set 2) and touchpad (ELAN0788 on i2c) accept no input for a few seconds. 2. Screen goes black, then the lock screen comes back and input works. ## Evidence (local journal, redacted) Lock itself succeeds fast before suspend, so this is not a lock-service failure: ``` 22:23:17 systemd-logind: Lid closed / Suspending... 22:23:17 omarchy-shell: lock-requested / lock-pending: screen-stabilizing 22:23:17 omarchy-shell: secure=true 22:23:17 systemd-sleep: Performing sleep operation 'suspend' (s2idle) 22:23:44 systemd-logind: Lid opened. 22:23:45 systemd-sleep: System returned from sleep operation 'suspend'. ``` The display driver fails panel link training on resume — and keeps failing afterwards: ``` i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:508:eDP-1][ENCODER:507:DDI A/PHY A][DPRX] Failed to enable link training ``` Seen at 22:23:44 (resume), then again 22:24:01, 22:24:41, 22:26:45 with no further suspends. Also on resume: `i915 raw-wakerefs=1 wakelocks=1 on cleanup` warning and an nvidia-drm flip-event warning. `/sys/power/mem_sleep` offers only `[s2idle]` (no deep S3), kernel `7.2.5-3-omarchy`, Hyprland 0.56.2, BIOS F.18. Related but distinct from #8112 (sleep-lock inhibitor race): that failure line also appears here (`Failed to inhibit: already running` on the respawned monitor), but the lock had already gone secure, so it does not explain the flicker/dead input. ## Likely contributors in Omarchy defaults/user config - `~/.config/hypr/monitors.lua` forced `eDP-1` to `1920x1080@144` (panel max) and forced `HDMI-A-1` to `1920x1080@60` at a fixed position even with nothing plugged in (`hyprctl monitors all -j` shows only eDP-1). Every resume therefore does a 144Hz eDP modeset known-flaky with PSR on this iGPU, plus a dead-output probe. - The shell holds the session lock 500ms for screen stabilization (`lock/Service.qml` `sessionLockStabilizeTimer`), which is correct, but the password field is presented before the i2c input devices finish re-probing, so first-seconds typing goes nowhere. ## Local workaround applied (safe, no reboot) - `eDP-1` → `1920x1080@60`, `HDMI-A-1` → `mode preferred, position auto` so resume is a single clean 60Hz modeset. `hyprctl configerrors` clean, `hyprctl monitors` confirms 60Hz. Still to test across several lid cycles; kernel option `i915.enable_psr=0` not yet tried (needs Limine cmdline + reboot). ## Suggestions for Omarchy 1. Do not ship/encourage a forced HDMI rule when no external monitor is connected — prefer `preferred/auto` or commented-out, so resume does one eDP modeset. 2. Consider calling out 144Hz + PSR resume flakiness (or a 60Hz fallback note) for Raptor Lake-P BOE panels. 3. Consider gating password-field focus/accept on input-device readiness after resume, or showing a brief 'waking devices…' state, since the lock currently looks ready while i2c input is still down.
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.
- Decided by agents · verified: partly in the audited area (lock)
The outcome (valid, duplicate, not a bug, …) is not decided yet.