Proof Portal

Sign in
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-5189GitHub issuePublicDecided· Duplicate

Hibernate resume UX: black screens, lock screen not auto-focusing, no progress indication

Reported by jfdnet · filed Oct 7, 2026 · open at source

Open at source
Decided: Duplicate — decided by agents · verified 3 days ago.
Duplicate of[Quattro] Lock password field can lose focus after suspend resume R-1214

R-1214 is the earliest report of this defect — filed Aug 30, 2026, open upstream. This report (filed Oct 7, 2026) describes the same defect, so it is folded under it in the inbox.

Decided by agents · verified· Oct 8, 2026

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?
AreaPartly in the audited arealock· 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

Hibernate resume UX: black screens, lock screen not auto-focusing, no progress indicationrevision 1 · captured 2026-10-07 02:47 UTC via poll

System details

  • Laptop: MECHREVO YAO SHI (Intel Core Ultra 7 356H, Panther Lake)
  • GPU: Hybrid — Intel iGPU (primary, Aquamarine card0) + NVIDIA RTX 5060 Laptop GPU
  • Kernel: 7.2.5-3-omarchy
  • Driver: nvidia-open-dkms 615.71.09
  • Boot: Limine UKI, LUKS-encrypted btrfs root, swapfile-based hibernation
  • Omarchy: Latest stable (Quattro)

What works

Hibernation itself works correctly on this hybrid GPU laptop with the community-verified configuration from #5554:
- NVreg_PreserveVideoMemoryAllocations=0
- NVreg_UseKernelSuspendNotifiers=1
- Image writes to disk, system fully powers off, session restores with all applications intact.

The UX problem

The hibernate entry and resume experience has several rough edges that make it feel unpolished compared to suspend:

Hibernate entry

  1. Screen locks (via before_sleep_cmd) — no visual feedback that hibernation is in progress
  2. System sits on the lock screen for ~16 seconds while the image is written to disk (10GB at ~640 MB/s)
  3. Then powers off abruptly — no transition animation or progress bar

Resume (after pressing power button)

  1. Plymouth LUKS unlock prompt appears (expected)
  2. After LUKS unlock, several black screen flashes while GPU and display reinitialize
  3. Lock screen eventually appears but is not auto-focused — user must press a key to activate the password field (same issue as #7467 and #6858, but specifically during hibernate resume)
  4. After entering lock screen password, desktop restores correctly

Double password entry

User must enter two passwords on resume: LUKS disk encryption password, then the session lock screen password. This is architecturally correct but could benefit from PAM integration or auto-unlock of the session after LUKS (some distros do this via pam_exec).

Related issues

  • #5554 — NVIDIA hibernate meta issue (driver-level fix)
  • #7467 — Lock screen not focusing after timeout
  • #6858 — Lock screen auto-focus not working
  • #7749 — Lock screen re-blanks slow DPMS monitors

Suggestion

These could be tracked as a hibernate UX polish epic:
1. Progress indication during image write (Plymouth or custom)
2. Smooth transition from lock screen to power-off state
3. Auto-focus lock screen password field on resume (fixes the key-press requirement)
4. Investigate Plymouth splash during hibernate resume to mask GPU reinit black screens
5. Consider PAM-based session auto-unlock after LUKS (optional, security tradeoff)

View raw text
## System details

- **Laptop**: MECHREVO YAO SHI (Intel Core Ultra 7 356H, Panther Lake)
- **GPU**: Hybrid — Intel iGPU (primary, Aquamarine card0) + NVIDIA RTX 5060 Laptop GPU
- **Kernel**: 7.2.5-3-omarchy
- **Driver**: nvidia-open-dkms 615.71.09
- **Boot**: Limine UKI, LUKS-encrypted btrfs root, swapfile-based hibernation
- **Omarchy**: Latest stable (Quattro)

## What works

Hibernation itself works correctly on this hybrid GPU laptop with the community-verified configuration from #5554:
- `NVreg_PreserveVideoMemoryAllocations=0`
- `NVreg_UseKernelSuspendNotifiers=1`
- Image writes to disk, system fully powers off, session restores with all applications intact.

## The UX problem

The hibernate entry and resume experience has several rough edges that make it feel unpolished compared to suspend:

### Hibernate entry
1. Screen locks (via `before_sleep_cmd`) — no visual feedback that hibernation is in progress
2. System sits on the lock screen for ~16 seconds while the image is written to disk (10GB at ~640 MB/s)
3. Then powers off abruptly — no transition animation or progress bar

### Resume (after pressing power button)
1. Plymouth LUKS unlock prompt appears (expected)
2. After LUKS unlock, several **black screen flashes** while GPU and display reinitialize
3. Lock screen eventually appears but is **not auto-focused** — user must press a key to activate the password field (same issue as #7467 and #6858, but specifically during hibernate resume)
4. After entering lock screen password, desktop restores correctly

### Double password entry
User must enter two passwords on resume: LUKS disk encryption password, then the session lock screen password. This is architecturally correct but could benefit from PAM integration or auto-unlock of the session after LUKS (some distros do this via `pam_exec`).

## Related issues
- #5554 — NVIDIA hibernate meta issue (driver-level fix)
- #7467 — Lock screen not focusing after timeout
- #6858 — Lock screen auto-focus not working
- #7749 — Lock screen re-blanks slow DPMS monitors

## Suggestion

These could be tracked as a hibernate UX polish epic:
1. Progress indication during image write (Plymouth or custom)
2. Smooth transition from lock screen to power-off state
3. Auto-focus lock screen password field on resume (fixes the key-press requirement)
4. Investigate Plymouth splash during hibernate resume to mask GPU reinit black screens
5. Consider PAM-based session auto-unlock after LUKS (optional, security tradeoff)

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

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.

  • DuplicateR-1214Decided by agents · verified · 2026-10-08 23:44 UTC