Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - slimlock

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: slimlock 1.3.6-1

Git Clone URL: https://aur-dev.archlinux.org/slimlock.git (read-only)
Package Base: slimlock
Description: Unholy screen locker (without SLiM)
Upstream URL: http://slim.berlios.de/
Licenses: GPL2
Conflicts: slim>=1.3.6, slimlock-git
Submitter: None
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 89
Popularity: 0.002424
First Submitted: 2010-12-24 22:51
Last Updated: 2015-06-12 21:50

Latest Comments

1 2 3 4 5 6 Next › Last »

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.

See: http://developer.berlios.de/project/shownotes.php?release_id=19463
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.