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.
Update to 4.0.4: NVIDIA hybrid laptop hard-freezes ~5 s after login once linux-omarchy is the default kernel (prebuilt nvidia-open has no modules for it)
Reported by Nord-Nogare · filed Sep 16, 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
- Omarchy 4.0.3-1 → 4.0.4-1 (update ran 2026-09-16; 4.0.4 released 2026-09-15) - Lenovo laptop, hybrid graphics: Intel iGPU + NVIDIA RTX 4070 Max-Q (AD106M, 10DE:2860), supergfxctl/supergfxd + nvidia-powerd active, Hyprland/Wayland - Driver: nvidia-open 610.57.04-14 (PREBUILT) — note: omarchy's install/hardware/nvidia.sh installs nvidia-open-dkms, so this machine diverges from the intended setup
What's wrong?
What happened
The update rolled in omarchy 4.0.4 (and omarchy-settings 4.0.4) and installed the custom kernel linux-omarchy 7.2.5-3 + headers. 4.0.4 makes linux-omarchy the DEFAULT boot kernel. Every boot on 7.2.5-3-omarchy hard-freezes ~5 s after login (keyboard/mouse dead, no panic, no log flush); only a forced power-off recovers. Booting the stock linux 7.2.3-arch1-3 entry works perfectly, with the exact same userspace.
Evidence
Boot correlation (all frozen boots were on 7.2.5-3-omarchy, all working boots on 7.2.3-arch1-3; journals end abruptly with zero kernel errors):
- frozen: 21:16–21:21, 21:23–21:26, 21:58–22:07, 22:23:48–22:24:20 on
7.2.5-3-omarchy - fine: all boots on
7.2.3-arch1-3
Identical lines at login in every frozen boot:
systemd-modules-load: Failed to find module 'nvidia_uvm'
supergfxd: ERROR supergfxctl::controller Action thread errored: The module nvidia_drm is missing
nvidia-powerd: ERROR! Allocate Root client failed 0x59
bash: /usr/lib/modules/7.2.3-arch1-3/ is owned by nvidia-open 610.57.04-14
Root cause: the prebuilt nvidia-open modules exist only under /usr/lib/modules/7.2.3-arch1-3/extramodules/ (built for the stock kernel); there are no NVIDIA modules for linux-omarchy, so the hybrid-graphics services fail and the desktop locks up.
Expected
An update that changes the default kernel should not land with the default entry missing the NVIDIA modules — at minimum warn, or keep the current kernel as default until compatible modules exist (same theme as #5706). A hard freeze is a harsh failure mode for the common NVIDIA-laptop path.
View raw text
### System details - Omarchy 4.0.3-1 → 4.0.4-1 (update ran 2026-09-16; 4.0.4 released 2026-09-15) - Lenovo laptop, hybrid graphics: Intel iGPU + NVIDIA RTX 4070 Max-Q (AD106M, 10DE:2860), supergfxctl/supergfxd + nvidia-powerd active, Hyprland/Wayland - Driver: nvidia-open 610.57.04-14 (PREBUILT) — note: omarchy's install/hardware/nvidia.sh installs nvidia-open-dkms, so this machine diverges from the intended setup ### What's wrong? ## What happened The update rolled in omarchy 4.0.4 (and omarchy-settings 4.0.4) and installed the custom kernel `linux-omarchy 7.2.5-3` + headers. 4.0.4 makes `linux-omarchy` the DEFAULT boot kernel. Every boot on `7.2.5-3-omarchy` hard-freezes ~5 s after login (keyboard/mouse dead, no panic, no log flush); only a forced power-off recovers. Booting the stock `linux 7.2.3-arch1-3` entry works perfectly, with the exact same userspace. ## Evidence Boot correlation (all frozen boots were on 7.2.5-3-omarchy, all working boots on 7.2.3-arch1-3; journals end abruptly with zero kernel errors): - frozen: 21:16–21:21, 21:23–21:26, 21:58–22:07, 22:23:48–22:24:20 on `7.2.5-3-omarchy` - fine: all boots on `7.2.3-arch1-3` Identical lines at login in every frozen boot: systemd-modules-load: Failed to find module 'nvidia_uvm' supergfxd: ERROR supergfxctl::controller Action thread errored: The module nvidia_drm is missing nvidia-powerd: ERROR! Allocate Root client failed 0x59 bash: /usr/lib/modules/7.2.3-arch1-3/ is owned by nvidia-open 610.57.04-14 Root cause: the prebuilt `nvidia-open` modules exist only under /usr/lib/modules/7.2.3-arch1-3/extramodules/ (built for the stock kernel); there are no NVIDIA modules for `linux-omarchy`, so the hybrid-graphics services fail and the desktop locks up. ## Expected An update that changes the default kernel should not land with the default entry missing the NVIDIA modules — at minimum warn, or keep the current kernel as default until compatible modules exist (same theme as #5706). A hard freeze is a harsh failure mode for the common NVIDIA-laptop path.
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 14:28 UTC