Package Details: slimlock 1.3.6-1

Git Clone URL: (read-only)
Package Base: slimlock
Description: Unholy screen locker (without SLiM)
Upstream URL:
Licenses: GPL2
Conflicts: slim>=1.3.6, slimlock-git
Submitter: None
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 86
Popularity: 0.000000
First Submitted: 2010-12-24 22:51
Last Updated: 2017-12-29 01:07

Latest Comments

WorMzy commented on 2014-11-05 07:10

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

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

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

WorMzy commented on 2014-05-16 12:35

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

jleclanche commented on 2014-05-16 12:18

Anyone else having trouble finding freetype headers?

blackshark commented on 2013-10-12 11:11

Can we currently execute 'slimlock' to lock the screen, or there exist another command ?

5chdn commented on 2013-10-09 08:59

In case any of you wants to upgrade to slim with slimlock, read on:

If you use the package extra/slim from pacman, you simply have do:
1) Backup your /etc/slimlock.conf
2) Remove your aur/slimlock installation
3) Update extra/slim to >= 1.3.6
4) Restore your /etc/slimlock.conf

Slim will read the slimlock.conf now, same behaviour as before. Simple as that.

5chdn commented on 2013-10-09 08:46

Slim conflicts with Slimlock now because it got merged into Slim.

Slim: Changes: 1.3.6 - 2013.10.01 * Merge slimlock

1ace commented on 2013-10-04 15:32

Out-of-date: it now conflicts with one of its own dependencies...

tuomo commented on 2013-10-04 13:45

This seems to be included in the official slim package now.

Diego commented on 2013-06-02 13:18

sorry but I don't see the tag 0.12 but only 0.11

Diego commented on 2013-06-02 13:13

ok... now i'm on work on it

KenjiTakahashi commented on 2013-05-03 03:23

There is a new tagged version (0.12) at dannyn repo. Should this package be updated to it?

Diego commented on 2013-04-17 11:43


Samuel commented on 2013-04-17 07:59

Folder name in ZIP-archive changed from slimlock-ABANDONED-master to slimlock-master.
Patch for the PKGBUILD to correct the paths:

Samuel commented on 2013-04-17 07:50

Folder name in ZIP-archive changed from slimlock-ABANDONED-master to
slimlock-master. Following patch for the PKGBUILD corrects the paths:

< cd "$srcdir/slimlock-ABANDONED-master"
> cd "$srcdir/slimlock-master"
< cd "$srcdir/slimlock-ABANDONED-master"
> cd "$srcdir/slimlock-master"

Anonymous comment on 2013-04-16 22:56

/tmp/packerbuild-0/slimlock/slimlock/PKGBUILD: line 19: cd: /tmp/packerbuild-0/slimlock/slimlock/src/slimlock-ABANDONED-master: No such file or directory
==> ERROR: A failure occurred in build().

Diego commented on 2013-03-22 00:52

the merge between slim and slimlock is started;a=commit;h=fccae89bbf97eb77b3c7a6c55b37ffa9c60eeaee
Someone could tell to dannyn?

Diego commented on 2013-03-22 00:45

the merge between slim and slimlock started;a=commit;h=fccae89bbf97eb77b3c7a6c55b37ffa9c60eeaee

Diego commented on 2013-03-22 00:43

@joelb the merge of slimlock into slim is started;a=commit;h=fccae89bbf97eb77b3c7a6c55b37ffa9c60eeaee

Anonymous comment on 2013-03-14 23:42

I don't think anyone would use a package called "slimlock-abandoned". Please don't make that.

My repo is where it started and I think it would make a certain amount of sense to keep it as the official repo. However it also makes some sense to move over to dannyn's repo. I have given him push access to my repo so it would be great if he would push his changes back to mine. Anyway, it doesn't matter whose repo is the main one, but this package should point to an stable release, ie a git tag named v1.x, which github will make a tarball for.

Diego commented on 2013-03-14 17:31

@Beini Tomorrow I could made a package called slimlock-abandoned where'll move this PKGBILD and here, however, I could use the repository that you have indicated

Diego commented on 2013-03-14 17:28

@joelb I don't know anything of coding XD. Then the repo is not the official one? Is only an unofficial forked repo... right?
Is the only official repo?

Anonymous comment on 2013-03-14 17:15

This package should point to a stable release - ie v1.x.tar.gz rather than master.tar.gz. Diego - if you're serious about maintaining this package I can change the repo name back to slimlock and give you access.

Anonymous comment on 2013-03-14 16:12

Well, the package already points to 'master' of the git repo, so I don't see why it shouldn't be changed.

Diego commented on 2013-03-13 14:53

it's a git repo and this is a stable package. Sorry. Ask to mantainer of slimlock-git to update or disown the package and I'll be happy to update it.

Anonymous comment on 2013-03-13 13:49

Looks like it's maintaned once again, new url:

Diego commented on 2013-01-23 09:09


Diego commented on 2013-01-17 09:09

This is new URL

Anonymous comment on 2012-12-05 13:41

You can use the abandoned repository with this patch:

3V0LU710N commented on 2012-05-27 22:54

Please add 'slim' to the depends array... =)

Anonymous comment on 2012-05-19 00:02

I seem to be receiving a segmentation fault whenever I start the program. It does work sometimes, however, so the problem seems to be random.

railla commented on 2012-04-06 07:39

>> I'm working on the freezing problem, but unfortunately I haven't been able to reproduce it.

@joelb, actually it's quite simple: you just need to leave slimlock for a day or so.
e.g., this issue reproduces every time I leave computer at work locked, and next morning I just have to do "killall slimlock" from the console to unlock it =]

larchunix commented on 2012-01-25 20:32

AFAIK, it is possible to disable CtrlAltBackspace by using "setxkbmap -option" before locking screen.

You can then activate it again with "setxkmap -option terminate:ctrl_alt_bksp" after unlocking screen.

Anonymous comment on 2012-01-20 04:13

@Tuxe See

tuomo commented on 2012-01-17 22:10

I really like the idea behind this program. However, pressing Ctrl+Alt+Backspace after locking my screen caused slimlock and/or X to crash somehow and forced me to reboot. Is this a bug in slimlock?

Ninquitassar commented on 2012-01-10 20:24

From term:
[1] 1816 segmentation fault slimlock

but when i run it with a key combination, it correctly runs. Any ideas?

The problem is also reported here:

Ninquitassar commented on 2012-01-10 20:23

From term:
[1] 1816 segmentation fault slimlock

but when i run it with a key combination, it correctly runs. Any ideas?

Anonymous comment on 2011-12-27 22:23

@skydrome you can use xidle to do that: xidle -timeout 60 -program /usr/bin/slimlock &

Anonymous comment on 2011-12-13 21:38

@skydrome most people use a key combination. I'm using mod-shift-l in xmonad (mod-l was taken).

skydrome commented on 2011-12-13 00:46

oh i see now. It would be nice to see it do some some sort of forking and activate on a period of inactivity instead of relying on the user to invoke it manually everytime you leave the comp.

Anonymous comment on 2011-12-13 00:07

@skydrome that's pretty much it. All it does is lock your screen. Turn it on while you're away so nobody can access your computer, then unlock it when you get back.

skydrome commented on 2011-12-12 06:37

when i run slimlock, the screen locks and after i unlock, slimlock terminates..
how is this supposed to be used? I use the xfce environment

Mex commented on 2011-11-23 17:53

seg faults after unlocking

Anonymous comment on 2011-10-25 17:29

Alex1985: That's right, I removed the ability to switch tty's, as a security feature. I'm working on the freezing problem, but unfortunately I haven't been able to reproduce it. Sorry, I don't know anything about xscreensaver so I can't answer your question.

Anonymous comment on 2011-10-25 07:35

Great package!
See that I use Slim to start Openbox is great to have the same login theme on the lock screen... anyway...

- I'm not able to switch to tty(n) after i give slimlock command (in any case and every time). Think is related to bug correction reported by orschiro.
- As jsteel reported, sometimes it freeze after suspend for a long time.

one question:
is there a way to use it as xscreensaver locker instead of xscreensaver standard one???


jsteel commented on 2011-10-02 14:07

Since the upgrade to 0.10.1 it sometimes freezes when I resume from suspend (cannot type anything). The mouse still moves. I have to kill my computer since I cannot switch tty.

mika.fischer commented on 2011-09-29 17:54

Thanks, the fix works fine.

Anonymous comment on 2011-09-28 21:48

mika.fischer: I added /etc/pam.d/slimlock to the backup array so the behavior should now be correct.

mika.fischer commented on 2011-09-27 07:32

The slimlock package seems to unconditionally overwrite its PAM config in /etc/pam.d/slimlock. This is very bad since if the user modified it and slimlock changes it, you cannot login anymore. I think this file should be treated as a configuration file and not overwritten if changed by the user.

Anonymous comment on 2011-09-21 20:47

orschiro: The bug you reported has been fixed. Thank you!

orschiro commented on 2011-09-13 21:53

There is a major security leak which allows to change to another tty when the screen is locked. See .

Can this be fixed in the next release?


Anonymous comment on 2011-03-17 14:35

mikeym: I'm glad you like it! I would definitely welcome anyone who knows linux security better than me to take a look at the source.

mikeym commented on 2011-03-16 18:19

I have to say, first appearances this is really nice. just having spent way too much time trying to theme xscreensaver to mitigate some of the dialog skin horror, this is a nice change.

I would be interested to know what someone who knows their linux security would make of this.

Anonymous comment on 2011-01-14 16:07

Thank you, I've updated the pkgbuild.

mezcal commented on 2011-01-14 15:37

md5sum is not valid

Anonymous comment on 2010-12-26 19:45

I've been using it and it seems stable, but it hasn't been tested by other people. Please save what you're working on before testing it the first time in case you can't sign back in.

smoge commented on 2010-12-26 18:10

joelb, this is stable for real use?