Package Details: physlock 0.5-1

Git Clone URL: (read-only)
Package Base: physlock
Description: lightweight linux console locking tool
Upstream URL:
Licenses: GPL
Submitter: ber_t
Maintainer: ber_t
Last Packager: ber_t
Votes: 22
Popularity: 0.492491
First Submitted: 2011-01-02 16:46
Last Updated: 2015-12-19 13:49

Dependencies (0)

Required by (0)

Sources (1)

Latest Comments

ber_t commented on 2014-12-16 08:52

You're too fast, danmilon. You could have at least gave me like 10 minutes to also update my own AUR package...

danmilon commented on 2014-12-16 08:48

Version 0.4.5 is out.
See here

ber_t commented on 2013-06-08 10:08

Thanks trickyelf. Version 0.4.4 fixes this.

trickyelf commented on 2013-06-03 21:44

The binary should be moved out of /usr/sbin.

ber_t commented on 2012-09-13 20:08

Kind of late, but the systemd issue is resolved in version 0.4.3.

ber_t commented on 2012-06-28 06:23

I'll try to find the time to add a log facility to physlock, so I can get more information if you're willing to help me out.

Can you please file bug reports on github? They're much nicer to work with.

jsteel commented on 2012-06-27 18:03

I've found recently that now and again when trying to unlock my session, I hit Enter and it just goes down to the next line; it does not say "username's password:". If I type my password at this point, it is being shown while I type! So it's not working properly. I have no choice but to kill my computer. Sorry I'm not sure what logs would be useful to you.

xduugu commented on 2012-04-15 11:20

Just want to add that vlock -nsa works here, if that helps.

xduugu commented on 2012-04-15 09:37

I tried systemd today and noticed that physlock does not work anymore. When started, it just switches to an tty and shows the normal login prompt, not the physlock one. Switching to another console does not work (as intended) and I have to login into the current tty and kill physlock which is stuck at 100% cpu load. The following error message appears when I kill physlock:
physlock: vt.c:102: error: could not deallocate console # 3: Device or resource busy

Can anyone else confirm this issue?

ber_t commented on 2011-10-13 19:55

You can simply press the Return key at the password prompt, after using the `-u' option. The given user is then automatically selected. There's no need to type the full user name again.

All comments