### System details

AMD Ryzen 7 7735HS, Radeon 680M (Lenovo ThinkBook 14 G7 ARP), Goodix MOC fingerprint sensor (27c6:659a), Omarchy 4.0.4, fprintd 1.94.5, quickshell 0.3.1, systemd 261

### What's wrong?

When the fingerprint reader gets into a state where `pam_fprintd` fails immediately, the lock screen retries fingerprint auth every 250 ms with no backoff or limit. Each retry spawns a new PAM subprocess, so the machine stays busy for as long as it stays locked. In my case the laptop woke in a bag (lid sensor bounce) and spent 74 minutes locked, making **14,056 fingerprint attempts (~3/s)**, and came out noticeably hot. Fingerprint unlock also stops working until you unlock with the password.

**Trigger:** suspending while a fingerprint verify is in progress, e.g. lid closed while the lock screen is waiting for a finger (or while `sudo` is waiting on `pam_fprintd`). fprintd logs:

```
fprintd: Device reported an error during verify: Cannot run while suspended.
pam_fprintd(omarchy-lock-fingerprint:auth): ReleaseDevice failed: Release failed with error: The device is still busy with another operation, please try again later.
```

After resume, every attempt fails instantly:

```
quickshell.service.pam.subprocess: Error while authenticating: "Authentication service cannot retrieve authentication info" (code 9)
```

repeated about every 300 ms until a password unlock.

**Steps to reproduce** (with a fingerprint enrolled):
1. Lock the screen.
2. Close the lid straight away, without touching the sensor, so the laptop suspends mid-verify.
3. Wait about 10 seconds and open the lid.
4. Fingerprint unlock doesn't work, and `journalctl -f` shows the `Error while authenticating … (code 9)` loop.

**Why it loops:** in `shell/plugins/lock/Service.qml`, both `handleFingerprintFinished()` (on any non-success result) and `fingerprintPam.onError` call `fingerprintRetryTimer.restart()` (`interval: 250`, re-armed after every failure), so an instant failure becomes a tight loop.

**Suggested fix:** back off on consecutive immediate failures (for example 250 ms, then 1 s, 5 s, 30 s), or stop retrying after N instant failures until the next user input. Restarting the fingerprint attempt after `PrepareForSleep(false)` would also help with the resume case.

**Workaround** that restores fingerprint unlock after resume (and so stops the loop in this case):

```ini
# /etc/systemd/system/fprintd-resume-reset.service
[Unit]
Description=Release stuck fingerprint reader after resume
After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl --no-block try-restart fprintd.service

[Install]
WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target
```

With this enabled, the same steps give about 5 failed attempts, then fingerprint unlock works about 1 s after resume. The unbounded 250 ms retry is still worth fixing, since any other cause of a persistent `pam_fprintd` failure would produce the same busy loop.