Lock Screen Explorer v1.9.6
Lock the session the moment your security key is pulled out, and light the dark lock screen by plugging it back in.
Before you upgrade to v1.9.6
3 to fixUpdate to v1.9.5 or later: while root copied a staged boot screen directory, a subdirectory swapped for a symlink mid-copy could pull root-only files into the world-readable theme directory; the theme now reaches root as one archive that is checked and unpacked in a root-owned directory first.
Turn rotation on again and accept its one-time setup, which rewrites the root helper for the archive spool; until then each rotation asks for your password through pkexec.
What changed in v1.9.6
Two off-by-default rows under Security key in Settings, `Lock when the key is removed` and `Wake when the key is inserted`, also set with `omarchy-shell lock setLockOnKeyRemoval on` and `omarchy-shell lock setWakeOnKeyInsert on`. The custom, snapshot, clip and Terminal boot screen generators give each display its own slice of the Plymouth canvas, and `apply.sh` hands root one tar file instead of a directory.
Also: Key presence is rechecked after suspend; boot screens lay out per display on two displays of different shapes; boot themes reach root as one checked archive, and a rotation set up before v1.9.5 asks for its one-time setup again.
v1.9.6, with v1.9.5 as the archive handoff alone; update with `omarchy plugin update io.github.sirjul1337.lock-explorer && omarchy restart shell`. The key settings appear once a security key is set up and turned on in Settings.
Fixed and improved
Settings gains `Lock when the key is removed` and `Wake when the key is inserted` under the Security key row, both off by default and acting only on the key itself, not on other HID devices; also `omarchy-shell lock setLockOnKeyRemoval on` and `omarchy-shell lock setWakeOnKeyInsert on`.
A key unplugged while the session slept is no longer counted as present after wake; the hotplug watcher runs for the whole lock, a failed round waits for the device list to settle before it is counted, and a key plugged back in is offered again to an empty field even after switching to the password.
On two displays of different shapes, each display now gets its own slice of the canvas in the custom, snapshot, clip and Terminal boot screens, instead of the last-drawn background covering both; single display unchanged, and untested on a real two-display boot, so #38 stays open.
Seeded by @iluxav with Claude Code (osfeed), from the release's public sources. Each change links to its evidence.