$ the-wire · showcase
Omarchy fixes fingerprint lockout, kernel lands urgent x86, timer, perf fixes
By RepoJournal · Filed · About Linux · Composed from the cited sources · methodology
Omarchy's polkit stack drops faillock lockout after repeated password failures, and a suspend-wedged fprintd claim left lock screens rejecting input until its 30-second idle timer expired.
Defer to system-auth in the polkit stack written by fingerprint/FIDO2 setup basecamp/omarchy
The polkit config written by `omarchy setup security fingerprint` and `omarchy setup security fido2` omitted the defer to `system-auth`, which drops `pam_faillock` from the stack; on affected machines polkit password prompts have no lockout after repeated failures and the failures never reach the shared faillock tally.
Fix fingerprint enrollment and lock-screen recovery (#7158) basecamp/omarchy
A fingerprint verify still open when the machine suspends wedged fprintd's claim on the reader: the verify died with "Cannot run while suspended", the follow-up ReleaseDevice failed on the busy device, and every lock-screen attempt after resume was rejected until fprintd's own 30-second idle timer fired. The fix restarts fprintd after resume.
Retry systemd reload in the fingerprint recovery migration (#14260) basecamp/omarchy
If the reload failed, the migration stayed pending with the fingerprint recovery drop-in already installed; the retry now reloads existing configuration so completion means systemd actually applied the stop timeout, while leaving administrator changes intact.
Merge tag 'timers-urgent-2026-10-04' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip torvalds/linux
A regression in the hrtimer rearming path's task work flag management could leave task work items unprocessed; the fix clears TIF_HRTIMER_REARM from the exit work using the mask.
Merge tag 'locking-urgent-2026-10-04' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip torvalds/linux
Locking picks up a futex private hash use-after-free on resize and stops running the refcount kunit self-test when !CONFIG_KUNIT_ALL_TESTS. Elsewhere in today's urgent batch, x86 stops applying va_align to hugetlb mappings on AMD F15h systems with custom va_align.bits values and hides the ptrace header register offset macros behind __ASSEMBLER__ or __FRAME_OFFSETS to fix user-space build errors...
Action items
- → Re-run `omarchy setup security fingerprint` or `omarchy setup security fido2` on affected machines to restore pam_fai... basecamp/omarchy [immediate]
