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.
start-hyprland crash-restart drops the launch environment: Hyprland comes back with "No config file found"
Reported by am5188 · 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?
- 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
Hyprland crashed during a GPU hang (REG_WAIT storm on amdgpu). The
omarchy monitor-watch / start-hyprland recovery path restarted it, but the
restarted instance lost the launch environment:
Sep 21 22:55:09 uwsm_hyprland.desktop[2957032]: [cfg] Config is either explicit or special.
Sep 21 22:55:09 uwsm_hyprland.desktop[2957032]: [cfg] Config is lua, loading lua mgr
Sep 21 22:55:09 uwsm_hyprland.desktop[2957032]: WARN: No config file found; attempting to generate.
The original launch ("uwsm start -g -1 -e -D Hyprland hyprland.desktop"
from the omarchy.desktop session) carries the config environment; the
restart path spawns Hyprland without it, so it falls back to generating a
default config. The session then runs with no Omarchy config (no shell
autostart, no bar) and never recovers; the only fix is a reboot.
System: Omarchy 4.0.4, Hyprland 0.56.2, kernel 7.2.5-3-omarchy, AMD
HawkPoint1 iGPU. Original launch and the restart both live in the
uwsm_hyprland.desktop unit (restart parent PID 1620,
/usr/bin/start-hyprland).
Expected: a restarted Hyprland reuses the same environment and config as
the original launch, so the desktop comes back without manual recovery.
Filed by Opus 5 (1M context) via Claude Code.
View raw text
Hyprland crashed during a GPU hang (REG_WAIT storm on amdgpu). The
omarchy monitor-watch / start-hyprland recovery path restarted it, but the
restarted instance lost the launch environment:
Sep 21 22:55:09 uwsm_hyprland.desktop[2957032]: [cfg] Config is either explicit or special.
Sep 21 22:55:09 uwsm_hyprland.desktop[2957032]: [cfg] Config is lua, loading lua mgr
Sep 21 22:55:09 uwsm_hyprland.desktop[2957032]: WARN: No config file found; attempting to generate.
The original launch ("uwsm start -g -1 -e -D Hyprland hyprland.desktop"
from the omarchy.desktop session) carries the config environment; the
restart path spawns Hyprland without it, so it falls back to generating a
default config. The session then runs with no Omarchy config (no shell
autostart, no bar) and never recovers; the only fix is a reboot.
System: Omarchy 4.0.4, Hyprland 0.56.2, kernel 7.2.5-3-omarchy, AMD
HawkPoint1 iGPU. Original launch and the restart both live in the
uwsm_hyprland.desktop unit (restart parent PID 1620,
/usr/bin/start-hyprland).
Expected: a restarted Hyprland reuses the same environment and config as
the original launch, so the desktop comes back without manual recovery.
Filed by Opus 5 (1M context) via Claude Code.
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 17:01 UTC