Package Details: i3lock-git 2.6.r35.g105a86d-1

Git Clone URL: https://aur.archlinux.org/i3lock-git.git (read-only)
Package Base: i3lock-git
Description: An improved screenlocker based upon XCB and PAM
Upstream URL: http://i3wm.org/i3lock/
Licenses: MIT
Groups: i3-vcs
Conflicts: i3lock
Provides: i3lock
Submitter: Atsutane
Maintainer: badboy
Last Packager: badboy
Votes: 50
Popularity: 1.480764
First Submitted: 2009-05-01 11:26
Last Updated: 2015-06-09 15:22

Required by (13)

Sources (1)

Latest Comments

Atsutane commented on 2012-05-13 19:51

extra/cairo now supports xcb again so i3lock-git also supports cairo => This package is obsolete. Thanks for maintaining it.

speps commented on 2012-05-13 13:59

@Atsutane Hi Thorsten, i3lock-libcairo-git could be probably merged with this now, do you confirm? Thanks

sschober commented on 2012-01-02 15:12

D_GNU_SOURCE -DNOLIBCAIRO -DVERSION=\""2.2-4-g2dd03ce (2011-12-30)"\" -c -o i3lock.o i3lock.c
i3lock.c:26:16: fatal error: ev.h: No such file or directory
compilation terminated.
make: *** [i3lock.o] Error 1

I think `libev` should be a dependency as well :)

ChristophLSA commented on 2011-12-06 10:56

new dependency: extra/xcb-util-image

Anonymous comment on 2010-11-21 20:51

ah I see, thx

Atsutane commented on 2010-11-21 19:53

Take a look at `i3lock --help`.

https://bbs.archlinux.org/viewtopic.php?pid=854622#p854622

Anonymous comment on 2010-11-21 19:14

"man i3lock" mentions an -i --image option to specify an image instead of a color as background. Trying to use that option results in this message<.


i3lock: invalid option -- 'i'
i3lock: i3lock: Unknown option. Syntax: i3lock [-v] [-n] [-b] [-d] [-c color] [-p win|default] (compiled with NOLIBCAIRO)

tpavlic commented on 2010-07-30 14:36

I figured it out. For some reason, I had AUR/libiconv installed rather than just sticking with the iconv that comes with glibc.

Uninstalling libiconv and then RE-installing glibc fixed the problem. Now i3lock-git builds without any modifications.

tpavlic commented on 2010-07-30 14:14

In the PKGBUILD, changed:

make || return 1

to

LDFLAGS=-liconv make || return 1

and now it builds fine. (it appears to be an "upstream" problem because it clearly depends on iconv but doesn't link to it... but why does it build fine on your system?)

tpavlic commented on 2010-07-30 14:11

Adding

-liconv

to LDFLAGS in the Makefile (in the line where LDFLAGS+=-lpam) fixes the problem. Can you think of a reason why iconv is included on your setups but not on mine?

All comments