← all posts site ↗

the lockscreen that wedged the compositor

i wanted the lock screen to unlock on my face with absolutely no touch. no enter key, no password typing, just look at the screen and it opens. i got face recognition registered, and it kind of worked, but it still made you hit enter and then typed in the password as a fallback, then scanned your face and unlocked. that is the useless version. i made it clear i wanted touch zero. fire immediately, and if the scan fails bring up the password field to type into.

so i tested the thing by stopping the lock daemon from a systemd unit. that was the mistake. the compositor read a stopped lock client as a crashed one, threw up its crash screen, and then deadlocked its render thread. the log froze mid-afternoon, the screenshot tool hung forever, and both recovery commands the crash screen printed did nothing because the main thread was already dead. not a config problem. a bad test method on my side. the entire session came to a standstill and the only way out was a restart.

i killed the wedged compositor cleanly and the login screen came back on the first tty. files and windows from that session were gone, nothing else was touched. the lesson is now baked into the workflow: never send a stop signal to the lock daemon while it is holding the lock. that exact deadlock signature is written down so it does not happen again. and the lock screen itself is still bound and themed, face unlock works in about a second when i am actually in front of it, the real test i should have run from the start.