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.
Switching monitor input kills my hyprland session when...
Reported by wolfgangw · filed Sep 8, 2025Closed upstream on 2025-10-26 by ryanrhughes, as a duplicate of #26 (R-2251). GitHub close reason: duplicate.
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?
- Not yet mapped to any requirement or component.
- 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. No decision has been recorded yet.
Original report
System details
Omarchy v2.1.0, i7-4790K, NVIDIA 3060
What's wrong?
... the monitor did not sleep before switching back to Omarchy box.
Dual-input HP X34 monitor. The Omarchy system is on HDMI. There is another physical system on the other input (DisplayPort). But the crash is reproducible with that other system off.
So the Omarchy system is up and happy (sooo nifty the whole thing, wow and thank you!). alacritty and chrome running. I switch the monitor input away, to DisplayPort, and this happens:
- when I switch back to HDMI/Omarchy system right away, while the monitor is scanning DisplayPort and, thus, awake, the xdg-desktop-portal-hyprland process crashes, dies and restarts itself. The previously openend apps (alacritty and chrome) crashed and died in solidarity. I get an "empty" but fully functional desktop.
- when I wait for the monitor's DisplayPort scan to finish and let the monitor go to sleep and then switch back to HDMI/Omarchy everything is alive and fine.
(I'm giddy because I just noticed that difference - progress, yay!)
I've looked at Hyprland Wiki's https://wiki.hypr.land/Crashes-and-Bugs/#getting-the-log. But despite adding ``debug:disable_logs = false` to `~/config/hypr/hyprland.conf` I don't have `~/.cache` or `/run/user/1000/hypr/hyprland.log``. I'm doing that wrong, I reckon?
View raw text
### System details Omarchy v2.1.0, i7-4790K, NVIDIA 3060 ### What's wrong? ... the monitor did not sleep before switching back to Omarchy box. Dual-input HP X34 monitor. The Omarchy system is on HDMI. There is another physical system on the other input (DisplayPort). But the crash is reproducible with that other system off. So the Omarchy system is up and happy (sooo nifty the whole thing, wow and thank you!). alacritty and chrome running. I switch the monitor input away, to DisplayPort, and this happens: - when I switch back to HDMI/Omarchy system right away, while the monitor is scanning DisplayPort and, thus, awake, the xdg-desktop-portal-hyprland process crashes, dies and restarts itself. The previously openend apps (alacritty and chrome) crashed and died in solidarity. I get an "empty" but fully functional desktop. - when I wait for the monitor's DisplayPort scan to finish and let the monitor go to sleep and then switch back to HDMI/Omarchy everything is alive and fine. (I'm giddy because I just noticed that difference - progress, yay!) I've looked at Hyprland Wiki's https://wiki.hypr.land/Crashes-and-Bugs/#getting-the-log. But despite adding ```debug:disable_logs = false``` to ```~/config/hypr/hyprland.conf``` I don't have ```~/.cache``` or ```/run/user/1000/hypr/hyprland.log```. I'm doing that wrong, I reckon? [hyprctl.systeminfo.txt](https://github.com/user-attachments/files/22217929/hyprctl.systeminfo.txt) [journalctl.snippet.txt](https://github.com/user-attachments/files/22217935/journalctl.snippet.txt) [nvidia.params.txt](https://github.com/user-attachments/files/22217938/nvidia.params.txt) [proc.cmdline.txt](https://github.com/user-attachments/files/22217943/proc.cmdline.txt)
- hyprctl.systeminfo.txt
- journalctl.snippet.txt
- nvidia.params.txt
- proc.cmdline.txt
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.
No decision has been recorded yet.