physlock VS xsecurelock

When I resume after suspending, the tty prompt for physlock comes up, as intended. When I enter my password, though, it shows the desktop and lets me move around the mouse, but the keyboard does nothing.

I'm not familiar with the PinePhone, but since you're able to use fbkeyboard in VTs, it sounds like physlock might work for you. I just wrote a comment about it in another thread. Unfortunately it's not very amenable to customization.

I use and recommend physlock. It's the most security-focused screen locking utility I'm aware of. Upon activation, it switches out of the graphical session and into tty0 which helps mitigate both of your issues. It also locks TTY switching to prevent accessing a logged-in TTY while locked, which is something that I don't think most other screen lockers do.

I use physlock[0] which locks all of the ttys. I've had no issues.

[1] https://github.com/muennich/physlock

Anyone here use https://github.com/google/xsecurelock?

I found it while going through reddit.com/r/unixporn and looking at other peoples tiling window manager setups.

Hey there, I am using xsecurelock (https://github.com/google/xsecurelock, xsecurelock-git from AUR) since a while and I am very happy with it. I would like to go further with fingerprint authentication. I know how PAM works, rode the README but I am afraid to screw it up and get locked out.

How do I fix this hanging behavior? Would using, say, xsecurelock or slock resolve the issue?

I replaced i3lock with this https://github.com/google/xsecurelock

https://github.com/google/xsecurelock#security-design

Google's XSecureLock seems to be a good minimal alternative. As the name suggest, it's focused on security. For the screen-saving part it can utilize a number of program, including xscreensaver.

I'm surprised he doesn't mention XSecureLock. Its entire focus is on preventing issues like this with modularity and redundancy.

https://github.com/google/xsecurelock