Package Details: slimlock 1.3.6-3

Git Clone URL: (read-only, click to copy)
Package Base: slimlock
Description: Unholy screen locker (without SLiM)
Upstream URL:
Licenses: GPL2
Conflicts: slim, slimlock-git
Submitter: None
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 85
Popularity: 0.000000
First Submitted: 2010-12-24 22:51 (UTC)
Last Updated: 2019-02-11 09:32 (UTC)

Latest Comments

1 2 3 4 5 6 7 Next › Last »

WorMzy commented on 2020-09-03 15:39 (UTC)

Neither. This is just the standalone screenlocking component of slim from [extra].

lorddickfist commented on 2020-09-03 06:48 (UTC)

So does this handle logins as well or do I need to startx?

WorMzy commented on 2019-02-11 09:34 (UTC)

Oops, my bad! Fixed now.

gavinhungry commented on 2019-02-11 05:59 (UTC)


Whoops! You made it install to /eetc/pam.d !

WorMzy commented on 2019-02-11 00:02 (UTC)

Thanks for the heads up, gavinhungry. Update pushed.

gavinhungry commented on 2019-02-08 21:16 (UTC) (edited on 2019-02-08 21:17 (UTC) by gavinhungry)

If you have trouble with slimlock after updating to pambase 20190105.1-1, this is because of a change to the PAM base config:

Create /etc/pam.d/slimlock with the following:

auth  required

WorMzy commented on 2014-11-05 07:10 (UTC)

It conflicts with slim because the slim package comes with slimlock. This package is for people who just want the screenlocking program, and not the login manager.

vohof commented on 2014-11-05 06:28 (UTC)

I don't understand. Why does this conflict with slim? How will I be to use slim if this conficts with it.

msx commented on 2014-08-17 23:10 (UTC)

It's just me or "tty_lock 1" functionality is broken?

WorMzy commented on 2014-05-16 12:35 (UTC)

Check what owns /usr/include/ft2build.h, that's the file causing the problems, and it's not provided by any official Arch package.