i3lock/README.md

77 lines
1.9 KiB
Markdown
Raw Normal View History

2010-07-16 17:47:42 +02:00
i3lock - improved screen locker
===============================
i3lock is a simple screen locker like slock. After starting it, you will
see a white screen (you can configure the color/an image). You can return
2010-07-21 01:45:11 +02:00
to your screen by entering your password.
2009-03-11 22:17:00 +01:00
2010-07-16 17:47:42 +02:00
Many little improvements have been made to i3lock over time:
2009-03-11 22:17:00 +01:00
2010-07-16 17:47:42 +02:00
- i3lock forks, so you can combine it with an alias to suspend to RAM
(run "i3lock && echo mem > /sys/power/state" to get a locked screen
after waking up your computer from suspend to RAM)
2009-03-11 22:17:00 +01:00
2010-07-16 18:22:33 +02:00
- You can specify either a background color or a PNG image which will be
displayed while your screen is locked.
2009-03-11 22:17:00 +01:00
2010-07-16 17:47:42 +02:00
- You can specify whether i3lock should bell upon a wrong password.
2009-03-11 22:17:00 +01:00
2010-07-16 17:47:42 +02:00
- i3lock uses PAM and therefore is compatible with LDAP etc.
On OpenBSD i3lock uses the bsd_auth(3) framework.
2009-03-11 22:17:00 +01:00
2019-03-08 20:29:33 +01:00
Running i3lock
-------------
Ubuntu:
```
sudo apt-get install i3lock
```
For other operating systems, see Requirements and Building below.
2010-07-16 17:47:42 +02:00
Requirements
------------
- pkg-config
2010-07-16 17:47:42 +02:00
- libxcb
- libxcb-util
- libpam-dev
- libcairo-dev
- libxcb-xinerama
- libxcb-randr
2012-03-15 12:47:40 +01:00
- libev
- libx11-dev
- libx11-xcb-dev
- libxkbcommon >= 0.5.0
- libxkbcommon-x11 >= 0.5.0
2009-03-11 22:17:00 +01:00
Running i3lock
-------------
Simply invoke the 'i3lock' command. To get out of it, enter your password and
press enter.
On OpenBSD the `i3lock` binary needs to be setgid `auth` to call the
authentication helpers, e.g. `/usr/libexec/auth/login_passwd`.
2018-12-02 12:15:46 +01:00
Building i3lock
---------------
We recommend you use the provided package from your distribution. Do not build
i3lock unless you have a reason to do so.
First install the dependencies listed in requirements section, then run these
commands (might need to be adapted to your OS):
```
autoreconf --force --install
rm -rf build/
mkdir -p build && cd build/
../configure \
--prefix=/usr \
--sysconfdir=/etc \
--disable-sanitizers
make
```
Upstream
--------
Please submit pull requests to https://github.com/i3/i3lock