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-114GitHub issuePublicDecided· Out of scope

linux-omarchy 7.2.5-3: ThinkPad P50s (Skylake + NVIDIA Maxwell) never wakes from S3 suspend; stock `linux` works

Reported by scalicura · filed Sep 25, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 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

linux-omarchy 7.2.5-3: ThinkPad P50s (Skylake + NVIDIA Maxwell) never wakes from S3 suspend; stock `linux` worksrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Lenovo ThinkPad P50s (20FL000MUS), Intel Skylake-U (HD 520) + NVIDIA Quadro M500M/K620M (GM108GLM, nvidia-580xx-dkms 580.178.04), Omarchy 4.0.4-1, linux-omarchy 7.2.5-3

What's wrong?

Closing the lid suspends the laptop to S3 (deep), but it never wakes up. A hard power-off is the only way out.

Regression: my previous install started on the stock Arch linux kernel and was upgraded to linux-omarchy. On that install, suspend/resume failed on linux-omarchy but worked when I booted the original stock kernel, which was still installed. I then did a fresh Omarchy 4.0.4 install for testing (linux-omarchy only), and it hangs on the first lid close.

Steps to reproduce
1. Boot linux-omarchy 7.2.5-3.
2. Close the lid, or run systemctl suspend.
3. Try to wake it: open the lid, press the power button, press keys. Nothing happens.

Observations
- The power LED keeps pulsing, so the machine reaches S3; the failure is on resume, not on suspend entry.
- The last journal line of the hung boot is kernel: PM: suspend entry (deep). Nothing is logged afterwards.
- /sys/power/mem_sleep: s2idle [deep]. The firmware reports ACPI: PM: (supports S0 S3 S4 S5) (no S0ix).
- /proc/acpi/wakeup: LID, SLPB and XHCI are enabled.
- NVIDIA: PreserveVideoMemoryAllocations=1, TemporaryFilePath=/var/tmp, and nvidia-suspend/resume/hibernate services are enabled. nvidia-suspend.service completes successfully before sleep. The dGPU stays in runtime active (Maxwell has no RTD3).
- BIOS: originally reproduced on N1KET49W (1.36). Since updated to N1KET58W (1.45, 12/12/2022), Lenovo's final release; its changelog only covers security, microcode and Secure Boot fixes. Re-tested on 1.45: same result. It suspends (logind Lid closed → Suspending... → nvidia-suspend OK → Performing sleep operation 'suspend') and never wakes; hard power-off needed.

Possibly related
- #12190: linux-omarchy 7.2.5-3 hangs on suspend entry on an XPS 13 (s2idle, Wildcat Lake); stock 7.2.3 works.
- #12129: NVIDIA laptop on 7.2.5-3 sleeps but won't wake.

Glad to test a patched kernel or collect more data, such as pm_trace or pm_test results.

View raw text
### System details

Lenovo ThinkPad P50s (20FL000MUS), Intel Skylake-U (HD 520) + NVIDIA Quadro M500M/K620M (GM108GLM, `nvidia-580xx-dkms` 580.178.04), Omarchy 4.0.4-1, linux-omarchy 7.2.5-3

### What's wrong?

Closing the lid suspends the laptop to S3 (deep), but it never wakes up. A hard power-off is the only way out.

**Regression:** my previous install started on the stock Arch `linux` kernel and was upgraded to linux-omarchy. On that install, suspend/resume failed on linux-omarchy but **worked when I booted the original stock kernel**, which was still installed. I then did a fresh Omarchy 4.0.4 install for testing (linux-omarchy only), and it hangs on the first lid close.

**Steps to reproduce**
1. Boot linux-omarchy 7.2.5-3.
2. Close the lid, or run `systemctl suspend`.
3. Try to wake it: open the lid, press the power button, press keys. Nothing happens.

**Observations**
- The power LED keeps pulsing, so the machine reaches S3; the failure is on resume, not on suspend entry.
- The last journal line of the hung boot is `kernel: PM: suspend entry (deep)`. Nothing is logged afterwards.
- `/sys/power/mem_sleep`: `s2idle [deep]`. The firmware reports `ACPI: PM: (supports S0 S3 S4 S5)` (no S0ix).
- `/proc/acpi/wakeup`: LID, SLPB and XHCI are enabled.
- NVIDIA: `PreserveVideoMemoryAllocations=1`, `TemporaryFilePath=/var/tmp`, and nvidia-suspend/resume/hibernate services are enabled. `nvidia-suspend.service` completes successfully before sleep. The dGPU stays in runtime `active` (Maxwell has no RTD3).
- BIOS: originally reproduced on N1KET49W (1.36). Since updated to N1KET58W (1.45, 12/12/2022), Lenovo's final release; its changelog only covers security, microcode and Secure Boot fixes. **Re-tested on 1.45: same result.** It suspends (logind `Lid closed` → `Suspending...` → nvidia-suspend OK → `Performing sleep operation 'suspend'`) and never wakes; hard power-off needed.

**Possibly related**
- #12190: linux-omarchy 7.2.5-3 hangs on suspend entry on an XPS 13 (s2idle, Wildcat Lake); stock 7.2.3 works.
- #12129: NVIDIA laptop on 7.2.5-3 sleeps but won't wake.

Glad to test a patched kernel or collect more data, such as `pm_trace` or `pm_test` results.


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 18:21 UTC