No description
04026259e0
SessionLockHandler::unlock clears the lock and schedules a render, but never tells IdleNotifierState that the user is there. Unlock paths that produce no input event -- fingerprint and smartcard readers -- therefore leave the idle clock running across the entire lock period, and it is already past its timeouts by the time the session is unlocked. The visible result is that the screen stays off after a successful unlock until the user moves the mouse or presses a key, or that the session locks itself again seconds after being unlocked. Notifying activity for every seat in unlock() resets the timers the same way an input event would. Drafted with AI assistance (Claude Code); the change was reviewed, built and tested by me on real hardware as described. Signed-off-by: chris-010 <10660568+chris-010@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| cosmic-comp-config | ||
| data | ||
| debian | ||
| examples | ||
| resources | ||
| src | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| flake.lock | ||
| flake.nix | ||
| i18n.toml | ||
| LICENSE | ||
| Makefile | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||