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.
omarchy-shell (quickshell 0.3.1) crashes with EGL 0x3000/'fatal error: Invalid argument' when monitor powers off on idle (DPMS), then crash-loops
Reported by natoftheboonies · filed Aug 30, 2026Closed upstream on 2026-08-30 by its own reporter natoftheboonies. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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 4.0.1-1, Quickshell 0.3.1-1, Hyprland 0.56.2-1, Hyprland (hyprutils 0.14.1), kernel 7.1.9-arch1-2
- HP EliteDesk Mini (no internal panel), Intel Core i5-8500T, Intel UHD Graphics 630 (Coffee Lake)
- Single external monitor: MSI MP275Q 2560x1440@60 on DP-1
- Idle config (defaults, ~/.config/omarchy/shell.json): screensaver 150, lock 300
What's wrong
When the system goes idle (~150s) and the monitor powers down (DPMS), the omarchy shell (Quickshell) crashes and auto-relaunches. The relaunched shell re-enters the idle state and crashes again, producing a crash-loop roughly every 1.5-2 minutes until the user interacts or reboots. From the desktop it looks like "the screen tries to sleep then wakes itself up."
The machine never actually suspends (no suspend targets; omarchy-sleep-lock.service never triggers) -- this is purely idle/DPMS.
Observed crash signature (journalctl):
omarchy-shell: There are no outputs - creating placeholder screen
omarchy-shell: Got removal for monitor "FALLBACK" which was not previously tracked
omarchy-shell: Could not create EGL surface (EGL error 0x3000)
omarchy-shell: eglSwapBuffers failed with 0x300d
omarchy-shell: The Wayland connection experienced a fatal error: Invalid argument
omarchy-shell: Omarchy shell exited with status 255; relaunching.In a prior session the same output teardown happened on wake instead (could not wake the monitor from idle) -- same root cause.
Observed root cause
When the monitor powers down, Hyprland drops the real output and toggles the connector between the real output and the FALLBACK backstop output (repeated wl_output create/destroy; visible in xdg-desktop-portal-hyprland logs as it repeatedly binding wl_output for DP-1 then FALLBACK). The shell's layershell/EGL surfaces are tied to the real output, so the teardown breaks the GL surface -> fatal Wayland error -> crash. Hyprland/dpms itself survives; the crash is in the shell's rendering surface not surviving DPMS output loss.
Steps to reproduce
1. Boot into an Omarchy/Hyprland session on an external DisplayPort monitor.
2. Walk away and leave it idle > 150s so the screensaver runs and the monitor powers off.
3. In logs: shell logs no outputs - creating placeholder, then EGL error 0x3000 and fatal error: Invalid argument, then exited with status 255; relaunching, repeating until user input/reboot.
Expected
The shell (and its bar/lock layer) should survive monitor DPMS power-off and restore when the display wakes, not exit with status 255.
Diagnostics (not an omarchy-debug log running on this version): one boot showed 160 "no outputs - creating placeholder screen" events and 10 "Omarchy shell exited with status 255; relaunching" events. Confirmed reproduced in the current session (fresh omarchy restart shell, then idle -> crash again ~5min later).
View raw text
**System details** - Omarchy 4.0.1-1, Quickshell 0.3.1-1, Hyprland 0.56.2-1, Hyprland (hyprutils 0.14.1), kernel 7.1.9-arch1-2 - HP EliteDesk Mini (no internal panel), Intel Core i5-8500T, Intel UHD Graphics 630 (Coffee Lake) - Single external monitor: MSI MP275Q 2560x1440@60 on DP-1 - Idle config (defaults, ~/.config/omarchy/shell.json): screensaver 150, lock 300 **What's wrong** When the system goes idle (~150s) and the monitor powers down (DPMS), the omarchy shell (Quickshell) crashes and auto-relaunches. The relaunched shell re-enters the idle state and crashes again, producing a crash-loop roughly every 1.5-2 minutes until the user interacts or reboots. From the desktop it looks like "the screen tries to sleep then wakes itself up." The machine never actually suspends (no suspend targets; `omarchy-sleep-lock.service` never triggers) -- this is purely idle/DPMS. Observed crash signature (journalctl): ``` omarchy-shell: There are no outputs - creating placeholder screen omarchy-shell: Got removal for monitor "FALLBACK" which was not previously tracked omarchy-shell: Could not create EGL surface (EGL error 0x3000) omarchy-shell: eglSwapBuffers failed with 0x300d omarchy-shell: The Wayland connection experienced a fatal error: Invalid argument omarchy-shell: Omarchy shell exited with status 255; relaunching. ``` In a prior session the same output teardown happened on *wake* instead (could not wake the monitor from idle) -- same root cause. **Observed root cause** When the monitor powers down, Hyprland drops the real output and toggles the connector between the real output and the `FALLBACK` backstop output (repeated `wl_output` create/destroy; visible in `xdg-desktop-portal-hyprland` logs as it repeatedly binding `wl_output` for `DP-1` then `FALLBACK`). The shell's layershell/EGL surfaces are tied to the real output, so the teardown breaks the GL surface -> fatal Wayland error -> crash. Hyprland/dpms itself survives; the crash is in the shell's rendering surface not surviving DPMS output loss. **Steps to reproduce** 1. Boot into an Omarchy/Hyprland session on an external DisplayPort monitor. 2. Walk away and leave it idle > 150s so the screensaver runs and the monitor powers off. 3. In logs: shell logs `no outputs - creating placeholder`, then `EGL error 0x3000` and `fatal error: Invalid argument`, then `exited with status 255; relaunching`, repeating until user input/reboot. **Expected** The shell (and its bar/lock layer) should survive monitor DPMS power-off and restore when the display wakes, not exit with status 255. **Diagnostics** (not an `omarchy-debug` log running on this version): one boot showed 160 "no outputs - creating placeholder screen" events and 10 "Omarchy shell exited with status 255; relaunching" events. Confirmed reproduced in the current session (fresh `omarchy restart shell`, then idle -> crash again ~5min later).
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.