Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1490GitHub issuePublicDecided· Out of scope

Suspend breaks NVIDIA 580xx installs: gpu-screen-recorder sets PreserveVideoMemoryAllocations=1 but the required nvidia power services are never enabled

Reported by matjam · filed Aug 25, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

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

Suspend breaks NVIDIA 580xx installs: gpu-screen-recorder sets PreserveVideoMemoryAllocations=1 but the required nvidia power services are never enabledrevision 1 · captured 2026-09-28 21:24 UTC via poll
Correction: as first filed, this issue claimed every Omarchy NVIDIA install was affected. That was wrong. nvidia-utils ships /usr/lib/modprobe.d/nvidia-sleep.conf with NVreg_UseKernelSuspendNotifiers=1, and the driver README (610.57.04, Chapter on power management) states that with the open kernel modules video memory preservation "is handled automatically" under that parameter — the systemd services are needed only "for the proprietary driver or if kernel suspend notifiers are disabled". Open-module installs are configured correctly by package defaults. The defect below is real but confined to the nvidia-580xx path.

Affected

Installs where install/hardware/nvidia.sh selects the legacy proprietary driver (omarchy-hw-nvidia-without-gsp, i.e. pre-Turing cards: GTX 9xx/10xx era): nvidia-580xx-dkms + nvidia-580xx-utils.

What's wrong?

Omarchy installs gpu-screen-recorder in the base package set. Its Arch packaging ships /usr/lib/modprobe.d/gsr-nvidia.conf:

options nvidia NVreg_PreserveVideoMemoryAllocations=1

With that option, the 580-series driver requires suspend/resume to be driven through /proc/driver/nvidia/suspend by nvidia-suspend.service, nvidia-hibernate.service, and nvidia-resume.service (580.178.04 README, power management chapter). The 580 branch has no NVreg_UseKernelSuspendNotifiers support, so there is no automatic fallback. Omarchy never enables those services: install/hardware/nvidia.sh configures early KMS only, and grep -r nvidia-suspend over the repo returns nothing. nvidia-580xx-utils ships all three units (confirmed against the omarchy repo's file database), but disabled units do nothing.

Result: on a 580xx install, every suspend sleeps without the VRAM save the driver was told to depend on, and resume returns to corrupted GPU state.

Fix

  1. install/hardware/nvidia.sh: enable the three services when the 580xx driver is selected.
  2. Migration for existing installs, gated on nvidia-580xx-utils being installed.

PR to follow.

Related

#5894 (closed, unfixed) reported the services-disabled condition on Optimus laptops running Omarchy 3.8.

Filed by Claude Fable 5 via Claude Code.

View raw text
> **Correction:** as first filed, this issue claimed every Omarchy NVIDIA install was affected. That was wrong. nvidia-utils ships `/usr/lib/modprobe.d/nvidia-sleep.conf` with `NVreg_UseKernelSuspendNotifiers=1`, and the driver README (610.57.04, Chapter on power management) states that with the open kernel modules video memory preservation "is handled automatically" under that parameter — the systemd services are needed only "for the proprietary driver or if kernel suspend notifiers are disabled". Open-module installs are configured correctly by package defaults. The defect below is real but confined to the nvidia-580xx path.

### Affected

Installs where `install/hardware/nvidia.sh` selects the legacy proprietary driver (`omarchy-hw-nvidia-without-gsp`, i.e. pre-Turing cards: GTX 9xx/10xx era): `nvidia-580xx-dkms` + `nvidia-580xx-utils`.

### What's wrong?

Omarchy installs `gpu-screen-recorder` in the base package set. Its Arch packaging ships `/usr/lib/modprobe.d/gsr-nvidia.conf`:

```
options nvidia NVreg_PreserveVideoMemoryAllocations=1
```

With that option, the 580-series driver requires suspend/resume to be driven through `/proc/driver/nvidia/suspend` by `nvidia-suspend.service`, `nvidia-hibernate.service`, and `nvidia-resume.service` (580.178.04 README, power management chapter). The 580 branch has no `NVreg_UseKernelSuspendNotifiers` support, so there is no automatic fallback. Omarchy never enables those services: `install/hardware/nvidia.sh` configures early KMS only, and `grep -r nvidia-suspend` over the repo returns nothing. nvidia-580xx-utils ships all three units (confirmed against the omarchy repo's file database), but disabled units do nothing.

Result: on a 580xx install, every suspend sleeps without the VRAM save the driver was told to depend on, and resume returns to corrupted GPU state.

### Fix

1. `install/hardware/nvidia.sh`: enable the three services when the 580xx driver is selected.
2. Migration for existing installs, gated on nvidia-580xx-utils being installed.

PR to follow.

### Related

#5894 (closed, unfixed) reported the services-disabled condition on Optimus laptops running Omarchy 3.8.

Filed by Claude Fable 5 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 08:41 UTC