You are not logged in.
Hi,
I have systemd lock service that starts s(lim)lock after the sleep.target. This works fine so far, since s(lim)lock forces me to enter user's password. But, waiting some minutes without doing anything unlocks automatically. I habe checked the systemd status, but I have no idea what the problem actually is. Does anyone have the same experience?
% sudo systemctl status lock :(
lock.service - Lock X session using lock
Loaded: loaded (/usr/lib/systemd/system/lock.service; enabled)
Active: failed (Result: exit-code) since Thu 2013-10-24 07:27:15 CEST; 4min 43s ago
Process: 28356 ExecStart=/usr/bin/slimlock (code=exited, status=1/FAILURE)
Oct 23 22:41:29 x201 systemd[1]: Starting Lock X session using lock...
Oct 24 07:26:52 x201 slimlock[28356]: pam_unix(slimlock:auth): authentication failure; logname= uid=1000 euid=1000 tty= ruser= rhost= user=mkind
Oct 24 07:27:15 x201 systemd[1]: lock.service operation timed out. Terminating.
Oct 24 07:27:15 x201 slimlock[28356]: error unlocking console: Inappropriate ioctl for device
Oct 24 07:27:15 x201 slimlock[28356]: slimlock: Caught signal; dying
Oct 24 07:27:15 x201 systemd[1]: lock.service: control process exited, code=exited status=1
Oct 24 07:27:15 x201 systemd[1]: Failed to start Lock X session using lock.
Oct 24 07:27:15 x201 systemd[1]: Unit lock.service entered failed state.As you can see from the log, slimlock exits with status 1.
Offline