Package Details: i3lock-color 2.12-1

Git Clone URL: (read-only)
Package Base: i3lock-color
Description: An improved screenlocker based upon XCB and PAM with color configuration support
Upstream URL:
Keywords: i3 i3lock lock
Licenses: MIT
Conflicts: i3lock
Provides: i3lock, i3lock-color
Submitter: ibrokemypie
Maintainer: ibrokemypie
Last Packager: ibrokemypie
Votes: 14
Popularity: 1.367270
First Submitted: 2017-09-29 12:12
Last Updated: 2018-11-15 23:32

Required by (19)

Sources (1)

Latest Comments

jadenPete commented on 2018-11-16 19:08

configure: error: Package requirements (xcb-xrm) were not met:

Package 'xcb-xrm', required by 'virtual:world', not found

Try adding xcb-util-xrm as a dependency

stlaz commented on 2018-07-28 10:54

The sanitizers and debug should really go away. Removing them seems to make the whole thing faster, too.

Probably a a bit more obvious solution:

From f3041226fe2581dafcdaabfcbb13215aba5b5e3a Mon Sep 17 00:00:00 2001
From: Stanislav Laznicka <some@mail.tld>
Date: Sat, 28 Jul 2018 12:47:36 +0200
Subject: [PATCH] don't build with debug, make blur faster

 PKGBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index 10df53d..d2b91bd 100644
@@ -19,8 +19,8 @@ build() {
    sed -i -e 's:login:system-auth:' pam/i3lock 

    autoreconf -fi
-   ./configure --prefix="$pkgdir/usr/" --sysconfdir="$pkgdir/etc/"
-   make
+   ./configure --prefix="$pkgdir/usr/" --sysconfdir="$pkgdir/etc/" --enable-debug=no --disable-sanitizers
+    make

 package() {

hcnelson99 commented on 2018-07-11 18:07

This package is building the debug version of i3lock-color. The following patch fixes the PKGBUILD. As a side effect, this patch fixes any address sanitizer errors (asan isn't enabled for release builds).

diff --git a/PKGBUILD b/PKGBUILD
index [`10df53d`]( 100644
@@ -12,6 +12,11 @@ conflicts=('i3lock')

+prepare() {
+   cd "${srcdir}/${pkgname}-${_version}"
+   echo "${_version}" > I3LOCK_VERSION
build() {
        cd "${srcdir}/${pkgname}-${_version}"

ibrokemypie commented on 2018-04-11 02:45

@guardian added dependency

leak is an issue with the program itself, not package. see here.

@nekk1 pam file has been patched

guardian commented on 2018-03-08 12:26

After having built it successfully, I'm getting sanitizer errors upon exit:

================================================================= ==13288==ERROR: LeakSanitizer: detected memory leaks Direct leak of 512 byte(s) in 2 object(s) allocated from: #0 0x7f6137975ae9 in interceptor_malloc /build/gcc/src/gcc/libsanitizer/asan/ #1 0x7f6133e987ee (/usr/lib/ Indirect leak of 128 byte(s) in 4 object(s) allocated from: #0 0x7f6137975ce1 in interceptor_calloc /build/gcc/src/gcc/libsanitizer/asan/ #1 0x7f6133e98ed9 (/usr/lib/ Indirect leak of 20 byte(s) in 2 object(s) allocated from: #0 0x7f613790c3b1 in __interceptor_strdup /build/gcc/src/gcc/libsanitizer/asan/ #1 0x7f6133e981f5 in FcValueSave (/usr/lib/ SUMMARY: AddressSanitizer: 660 byte(s) leaked in 8 allocation(s).

guardian commented on 2018-03-08 12:19

PKGBUILD lacks a dependency on libjpeg-turbo

nekk1 commented on 2018-02-14 20:56

The provided .pam file is not reflecting the one in the community version, and it's causing the following errors in journalctl

Feb 14 21:38:08 xps i3lock[25031]: pam_tally(i3lock:auth): Error opening /var/log/faillog for update

Feb 14 21:38:08 xps i3lock[25031]: pam_tally(i3lock:auth): Error opening /var/log/faillog for read

Feb 14 21:38:08 xps i3lock[25031]: pam_tally(i3lock:setcred): Error opening /var/log/faillog for update

Feb 14 21:38:08 xps i3lock[25031]: pam_tally(i3lock:setcred): Error opening /var/log/faillog for update

The community PKGBUILD replaces 'login' with 'system-auth' to make this work:

I replaced it manually to test it out, and it works.

ibrokemypie commented on 2017-12-11 02:12

there is no make -j8 in the PKGBUILD...

S13ntist commented on 2017-12-10 11:55

Please don't use 'make -j8' in the PKGBUILD. This is horrible on a system with say 2 processors.

Things like this belong in the MAKEFLAGS env var in makepkg.conf and should only be lowered to -j1 if the build fails if done concurrently.