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.
[Quattro] Native lock screen loses all Wayland outputs and loops on dual DisplayPort monitors
Reported by SilentMutiny · filed Sep 21, 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: 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
System details
Omarchy 4.0.4-1; linux-omarchy 7.2.5-3-omarchy; AMD Navi 10 / amdgpu; 2× ViewSonic VG2755 via DisplayPort (DP-1 + DP-2), both 1920x1080@60; upgraded from Omarchy 3.x.
What's wrong?
Running omarchy-system-lock on Quattro causes both of my DisplayPort monitors to briefly go black. The native lock screen eventually reappears, but it repeatedly loops/reloads before I can finally enter my password and return to the desktop.
This is reproducible.
Steps:
1. Boot normally with both monitors active.
2. Run:
omarchy-system-lock- Both monitors black-screen, then the native lock screen loops/reloads.
Relevant logs:
omarchy lock ... lock-requested
omarchy lock ... secure=true
qt.qpa.wayland: There are no outputs - creating placeholder screen
Not creating lock surface ... as it is not backed by a valid wayland output
quickshell.hyprland.ipc: Got removal for monitor "FALLBACK" which was not previously trackedPAM authentication eventually succeeds and the session unlocks.
Troubleshooting completed:
- Updated to Omarchy 4.0.4-1 and rebooted into 7.2.5-3-omarchy.
- Moved old pre-Quattro ~/.config/hypr/hypridle.conf and hyprlock.conf out of the active config path.
- Rebooted after moving those files.
- Confirmed no hypridle or hyprlock process is running.
- Confirmed the Quattro shell is running:
quickshell -n -p /usr/share/omarchy/shellI can attach the full lock log and hyprctl monitors all output if useful.
View raw text
### System details Omarchy 4.0.4-1; linux-omarchy 7.2.5-3-omarchy; AMD Navi 10 / amdgpu; 2× ViewSonic VG2755 via DisplayPort (DP-1 + DP-2), both 1920x1080@60; upgraded from Omarchy 3.x. ### What's wrong? Running `omarchy-system-lock` on Quattro causes both of my DisplayPort monitors to briefly go black. The native lock screen eventually reappears, but it repeatedly loops/reloads before I can finally enter my password and return to the desktop. This is reproducible. Steps: 1. Boot normally with both monitors active. 2. Run: ```bash omarchy-system-lock ``` 3. Both monitors black-screen, then the native lock screen loops/reloads. Relevant logs: ```text omarchy lock ... lock-requested omarchy lock ... secure=true qt.qpa.wayland: There are no outputs - creating placeholder screen Not creating lock surface ... as it is not backed by a valid wayland output quickshell.hyprland.ipc: Got removal for monitor "FALLBACK" which was not previously tracked ``` PAM authentication eventually succeeds and the session unlocks. Troubleshooting completed: - Updated to Omarchy 4.0.4-1 and rebooted into `7.2.5-3-omarchy`. - Moved old pre-Quattro `~/.config/hypr/hypridle.conf` and `hyprlock.conf` out of the active config path. - Rebooted after moving those files. - Confirmed no `hypridle` or `hyprlock` process is running. - Confirmed the Quattro shell is running: ```text quickshell -n -p /usr/share/omarchy/shell ``` I can attach the full lock log and `hyprctl monitors all` output if useful.
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: in the audited area (lock)
The outcome (valid, duplicate, not a bug, …) is not decided yet.