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.
linux-omarchy 7.2.5-3: i915 GPU hang on Arrow Lake aborts Hyprland; watchdog restart loads default config
Reported by chiroro-jr · 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?
- AreaOutside the audited area· Decided by agents · verified
- 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
- Machine: ASUS Zenbook 14 UX3405CA
- CPU: Intel Core Ultra 9 285H (Arrow Lake)
- GPU: Intel Arrow Lake-P Arc Pro 130T/140T (
8086:7d51), driveri915(xe listed as alternate) - Omarchy: 4.0.4-1
- Kernel:
linux-omarchy 7.2.5-3(7.2.5-3-omarchy), first boot of this kernel (installed 2026-09-18 11:18, booted 11:35) - Previous kernel still installed:
linux 7.2.3.arch1-3(stock Arch) - Hyprland: 0.56.2-2 (
efb50993780079460b0cbed1363e2166a2de1d9f) - Mesa: 26.2.2-arch1.1
- Session: SDDM + uwsm (
start-hyprland)
omarchy debug --no-sudo --print was written to /tmp/omarchy-debug.log on this machine.
What's wrong
On the first boot of linux-omarchy 7.2.5-3, the Intel GPU hung, Hyprland aborted, and start-hyprland restarted the compositor in safe mode. The session came back as stock Hyprland (recoverycfg.lua / kitty+dolphin example) instead of Omarchy. User config under ~/.config/hypr/ was not deleted; a logout/login loaded hyprland.lua again.
This did not happen on stock linux 7.2.3 on this machine. There is one prior Hyprland SIGABRT on 2026-09-02, but the journal has no GPU HANG for that day.
Android Emulator (Pixel_7 AVD, hw.gpu.mode=host / gfxstream) was running at the time and also SIGSEGV'd during teardown after the compositor died. That follow-on crash is in Google's SDK qemu, not Omarchy.
Timeline (2026-09-18 CAT)
12:21 Pixel_7 emulator starts (host GPU)
12:22/25 i915: Atomic update failure on pipe A
12:42:08 i915: GPU HANG: ecode 12:1:84dffffb, in Hyprland [1523]
i915: Hyprland[1523] context reset due to GPU hang
12:42:09 Hyprland SIGABRT (assert in CHyprOpenGLImpl::begin during renderMonitor)
12:42:10 start-hyprland: "Hyprland exit not-cleanly, restarting"
[cfg] Config is either explicit or special.
WARN: No config file found; attempting to generate.
recoverycfg.lua written (autogenerated default)
12:43:10 user logout/login; hyprland.lua loads normallyHyprland crash report: /home/chiroro/.cache/hyprland/hyprlandCrashReport1523.txt
- Signal 6 (ABRT) after GPU reset
- Render::GL::CHyprOpenGLImpl::begin ← renderMonitor ← CMonitorFrameScheduler::onFrame ← DRM page flip
Not an OOM (no oom-kill in the journal).
Expected
GPU reset should not take down the Omarchy session. If Hyprland does abort, a watchdog restart should reload ~/.config/hypr/hyprland.lua, not generate stock defaults.
Actual
i915 hang → Hyprland abort → safe-mode recoverycfg.lua → looks like “lost my config” until logout/login.
Related
- #11563 — same safe-mode config drop, different crash (
hyprctlLuapop_back) - #10350 — same
CHyprOpenGLImpl::beginabort after i915 GPU hang, hybrid NVIDIA Pascal, not this Intel-only Arrow Lake laptop - #12238 —
linux-omarchy 7.2.5-3i915 FIFO underrun on Kaby Lake, not a GPU hang
Not bisected against stock linux 7.2.3 on this kernel version yet. Happy to retest on linux 7.2.3.arch1-3 or with the emulator on software GPU.
Filed by Cursor Grok 4.6 via Cursor.
View raw text
### System details
- Machine: ASUS Zenbook 14 UX3405CA
- CPU: Intel Core Ultra 9 285H (Arrow Lake)
- GPU: Intel Arrow Lake-P Arc Pro 130T/140T (`8086:7d51`), driver `i915` (xe listed as alternate)
- Omarchy: 4.0.4-1
- Kernel: `linux-omarchy 7.2.5-3` (`7.2.5-3-omarchy`), first boot of this kernel (installed 2026-09-18 11:18, booted 11:35)
- Previous kernel still installed: `linux 7.2.3.arch1-3` (stock Arch)
- Hyprland: 0.56.2-2 (`efb50993780079460b0cbed1363e2166a2de1d9f`)
- Mesa: 26.2.2-arch1.1
- Session: SDDM + uwsm (`start-hyprland`)
`omarchy debug --no-sudo --print` was written to `/tmp/omarchy-debug.log` on this machine.
### What's wrong
On the first boot of `linux-omarchy 7.2.5-3`, the Intel GPU hung, Hyprland aborted, and `start-hyprland` restarted the compositor in **safe mode**. The session came back as stock Hyprland (`recoverycfg.lua` / kitty+dolphin example) instead of Omarchy. User config under `~/.config/hypr/` was not deleted; a logout/login loaded `hyprland.lua` again.
This did not happen on stock `linux 7.2.3` on this machine. There is one prior Hyprland SIGABRT on 2026-09-02, but the journal has no `GPU HANG` for that day.
Android Emulator (Pixel_7 AVD, `hw.gpu.mode=host` / gfxstream) was running at the time and also SIGSEGV'd during teardown after the compositor died. That follow-on crash is in Google's SDK qemu, not Omarchy.
### Timeline (2026-09-18 CAT)
```
12:21 Pixel_7 emulator starts (host GPU)
12:22/25 i915: Atomic update failure on pipe A
12:42:08 i915: GPU HANG: ecode 12:1:84dffffb, in Hyprland [1523]
i915: Hyprland[1523] context reset due to GPU hang
12:42:09 Hyprland SIGABRT (assert in CHyprOpenGLImpl::begin during renderMonitor)
12:42:10 start-hyprland: "Hyprland exit not-cleanly, restarting"
[cfg] Config is either explicit or special.
WARN: No config file found; attempting to generate.
recoverycfg.lua written (autogenerated default)
12:43:10 user logout/login; hyprland.lua loads normally
```
Hyprland crash report: `/home/chiroro/.cache/hyprland/hyprlandCrashReport1523.txt`
- Signal 6 (ABRT) after GPU reset
- `Render::GL::CHyprOpenGLImpl::begin` ← `renderMonitor` ← `CMonitorFrameScheduler::onFrame` ← DRM page flip
Not an OOM (no oom-kill in the journal).
### Expected
GPU reset should not take down the Omarchy session. If Hyprland does abort, a watchdog restart should reload `~/.config/hypr/hyprland.lua`, not generate stock defaults.
### Actual
i915 hang → Hyprland abort → safe-mode `recoverycfg.lua` → looks like “lost my config” until logout/login.
### Related
- #11563 — same safe-mode config drop, different crash (`hyprctl` Lua `pop_back`)
- #10350 — same `CHyprOpenGLImpl::begin` abort after i915 GPU hang, hybrid NVIDIA Pascal, not this Intel-only Arrow Lake laptop
- #12238 — `linux-omarchy 7.2.5-3` i915 FIFO underrun on Kaby Lake, not a GPU hang
Not bisected against stock `linux 7.2.3` on this kernel version yet. Happy to retest on `linux 7.2.3.arch1-3` or with the emulator on software GPU.
Filed by Cursor Grok 4.6 via Cursor.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.
- Out of scopeDecided by agents · verified · 2026-10-09 15:32 UTC