## Summary

On a ThinkPad L13 Yoga Gen 3, the Omarchy lock screen intermittently becomes unusable after a normal `s2idle` resume. The built-in display wakes and the password prompt can appear, but input may not reach the lock service; the display can then go blank. A hard power-off has been required in affected cases.

This also occurs with no dock or external monitor attached. Connecting a monitor while the resumed lock screen is still active is a separate, more reproducible trigger which produces monitor-scale warnings, but it is not required for the base failure.

## Expected behaviour

After opening the lid, the built-in display should wake and the Omarchy password prompt should accept input reliably. Closing and reopening the lid should not leave the session unresponsive.

## Observed behaviour

- Resume completes at the kernel/systemd level.
- Built-in display turns on and the password prompt may be visible.
- The prompt does not respond to input, then the screen becomes blank.
- Re-closing/reopening the lid may repeat the issue.
- In the latest incident, no external display or dock was connected.

## Latest incident timeline

- `2026-09-23 18:31:07 +10`: entered `s2idle`.
- `2026-09-23 19:26:22 +10`: lid opened; resume completed. `amdgpu` reports `SMU is resumed successfully!`, followed by `PM: suspend exit`; systemd reports the suspend operation finished.
- `2026-09-23 19:27:10 +10`: lid closed; a second `s2idle` operation began.
- `2026-09-23 19:27:12 +10`: lid opened; second resume completed normally at kernel/systemd level.
- `2026-09-23 19:27:25 +10`: lid closed, then opened at `19:27:39`; no new suspend operation was logged before the forced shutdown.

There were no PAM password requests logged after the two resumes, despite the visible prompt, and no GPU reset, ring timeout, kernel panic, OOM kill, Hyprland/Quickshell crash, or coredump.

## Related monitor observation

In separate incidents, attaching a DP monitor/dock while the resumed session is still locked triggers repeated:

```text
gdk_monitor_set_scale: assertion `scale > 0.' failed
```

from `voxtype-osd-gtk4` and Nautilus. Unlocking first and attaching the monitor afterwards works. The latest no-dock incident did not produce these scale assertions.

## Fingerprint isolation

The lock-screen-only fingerprint PAM service was disabled after an earlier, separately diagnosed retry storm. It remains disabled for this incident; the fingerprint device re-enumerated on USB after resume but there were no fingerprint/PAM retry messages. The issue therefore persists independently of that retry storm.

## System

- Omarchy: `4.0.3-1`
- Kernel: `7.2.3-arch1-3`
- linux-firmware: `20260810-2`
- Mesa: `26.2.2-1`
- Hyprland: `0.56.2-2`
- Quickshell: `0.3.1-1`
- Laptop: Lenovo ThinkPad L13 Yoga Gen 3 (`21BB0056AU`)
- BIOS: `R1TET60W (1.39)`
- GPU: AMD integrated graphics (`amdgpu`)
- Available sleep mode: `[s2idle]` only

`omarchy debug --no-sudo --print` is not available in Omarchy `4.0.3-1` on this installation, so no generated Omarchy debug bundle is available.

## Reproduction

Not deterministic. The highest-confidence reproduction pattern so far is:

1. Leave the laptop asleep using lid-close (`s2idle`).
2. Open the lid.
3. Wait for the built-in display and password prompt.
4. On affected attempts, the prompt is visible but unresponsive and may become blank.

Connecting an external monitor before unlocking increases the likelihood of a visible display failure, but is not necessary.

I can provide more focused journal excerpts or a screen recording if there is a preferred collection method for the post-resume lock path.