Package Details: i3lock-color-git r898.32a1437-1

Git Clone URL: (read-only, click to copy)
Package Base: i3lock-color-git
Description: The world's most popular non-default computer lockscreen.
Upstream URL:
Keywords: i3 i3lock i3lock-color i3wm lock Raymo111 security x11 xorg
Licenses: MIT
Conflicts: i3lock
Provides: i3lock, i3lock-color
Submitter: brandon099
Maintainer: brandon099 (Raymo111)
Last Packager: Raymo111
Votes: 37
Popularity: 0.096996
First Submitted: 2015-08-13 22:44 (UTC)
Last Updated: 2022-01-24 06:32 (UTC)

Required by (46)

Sources (1)

Latest Comments

Raymo111 commented on 2020-11-23 01:29 (UTC)

Phew! Thanks @brandon099!

patrick96 commented on 2020-11-23 01:03 (UTC)

@brandon099 @Raymo111 Works perfectly now. Thanks!

brandon099 commented on 2020-11-23 00:42 (UTC)

Reverted out the removal of git as a make dependency, so all should be as it was :)

Raymo111 commented on 2020-11-22 16:49 (UTC)

Oh no! @patrick96 @brandon099 I'm so sorry.

patrick96 commented on 2020-11-22 16:29 (UTC)

Please add git back into makedepends, it is required to build the package and it is not in base-devel.

Not having git in makedepends breaks building in a clean chroot with aurutils, but also just with extra-x86_64-build.

Raymo111 commented on 2020-11-18 22:16 (UTC)

Oh... I'm mistaken then. Still, AUR is git-based so if you don't have git... I don't think that anyone is manually downloading PKGBUILDS :P

brandon099 commented on 2020-11-18 22:16 (UTC)

I've removed the git makedepends -- we can always revert that back if it breaks for people.

brandon099 commented on 2020-11-18 22:12 (UTC)

Git is not part of the base-devel group though.

Raymo111 commented on 2020-11-18 21:56 (UTC) (edited on 2020-11-18 21:56 (UTC) by Raymo111)

base-devel is a requisite though (see drScience's comment below). Besides, I've noticed that git is missing from many other -git packages as well? I'm not 100% sure though.

brandon099 commented on 2020-11-18 21:11 (UTC)

Building in a clean chroot does not succeed if Git is removed as a build dependency, so I'm not sure it's safe to assume all users will have base-devel installed.

Raymo111 commented on 2020-11-18 16:22 (UTC)

@brandon099 can you remove git from the list of dependencies? I thought it'd be just a simple web thing but I have to clone it and stuff (I'm in between laptops with no Arch at the moment) and I don't want to mess something up.

Raymo111 commented on 2020-11-18 16:18 (UTC)

@drScience no worries! I should remove git from the dependencies as well, since that's also in base-devel.

drScience commented on 2020-11-18 16:14 (UTC)

@Raymo111 Thanks for the quick reply, you're right (, I had installed base-devel but inadvertently removed auto-conf.

Raymo111 commented on 2020-11-18 15:22 (UTC)

@drScience correct me if I'm wrong, but aren't all packages from base-devel exempt from dependency listing, as they are assumed to be installed for packages in the AUR?

drScience commented on 2020-11-18 10:29 (UTC)

The build() function makes use of autoreconf, so shouldn't the autoconf ( package be listed as a dependency?

brandon099 commented on 2020-09-03 23:29 (UTC)

@oakszyjrnrdy, that has been added. @Raymo111 I've removed the sed hack.

Thanks all!

Raymo111 commented on 2020-09-03 22:28 (UTC)

@brandon99 can you remove the sed line and the preceding comment? I've fixed it upstream.

oakszyjrnrdy commented on 2020-08-07 21:56 (UTC)

/etc/pam.d/i3lock should be added into backup array in PKGBUILD in order to generate .pacnew file when updated if this file is modified by users.

It's common to modify /etc/pam.d/i3lock to use fingerprint to unlock.

Raymo111 commented on 2020-03-10 22:43 (UTC)

@brandon099 No worries, I will enjoy it moving forward. Also, I'd love to co-maintain. That might make things easier. Not quite sure about what to do with the release process, but I'm all ears.

brandon099 commented on 2020-03-10 22:39 (UTC)

Updated -- thanks for taking over this fork @Raymo111

If you have any desire to co-maintain and automate this into your release process, let me know and I can add you.

Raymo111 commented on 2020-03-10 15:49 (UTC)

PandorasFox has transferred the repo to me, so please update the relevant URLs from to

brandon099 commented on 2018-08-13 22:02 (UTC)

Removed hard-coded -j8 and added the new xcb-xrm dependency.

jaantoots commented on 2018-07-08 15:06 (UTC)

Please remove "-j8" from make. This should be configured in the MAKEFLAGS variable in makepkg.conf as a system-wide option.

S13ntist commented on 2018-07-07 11:34 (UTC)

Missing dependency on xcb-util-xrm

Fails to build in clean chroot:

configure: error: Package requirements (xcb-xrm) were not met: Package 'xcb-xrm', required by 'virtual:world', not found

brandon099 commented on 2017-12-08 00:41 (UTC)

@Pandoras_Fox, thanks for the gist with most of the changes needed to support your changes in the Github repo. I made a few additional tweaks, and we should be all up-to-date now.

Pandoras_Fox commented on 2017-12-06 17:35 (UTC)

I figured that as long as the pkgbuild was changing, this was probably as good a time as any to get around to updating my github username.

Pandoras_Fox commented on 2017-12-06 03:27 (UTC)

actually, I think that you could do something like:

git tag aur_build && autoreconf -fi && ...

Feel free to make an issue on github or whatever if there's something I can do to make it easier.

Pandoras_Fox commented on 2017-12-06 03:20 (UTC)

This PKGBUILD is very likely to break when I update the package later today or tomorrow to match upstream (upstream moved to using gnu autotools, which has been kinda weird, but a bit useful for the address sanitization stuff).

I'm looking into forcing a way for the build process to not do a debug build if it's done from git. Currently, you'll want to do something like:

autoreconf -fi && ./configure && cd x86_64-pc-linux-gnu && make -j8

or something. There'll probably be an option for the ./configure or something, though.

brandon099 commented on 2017-10-01 23:52 (UTC)

@ibrokemypie: Just added i3lock-color to the provides. Thanks!

ibrokemypie commented on 2017-09-29 12:22 (UTC)

Hey, would you be able to add i3lock-color to the provides? I have put together packages for i3lock-color (the non-git version) and i3lock-next which requires i3lock-color (git or otherwise), something which cannot be fulfilled by other i3lock packages. Thanks!

Pandoras_Fox commented on 2017-09-13 18:07 (UTC)

Looks like the SSE stuff used for blurring is a large part of it; dunno when I'll be able to get around to working out what to do. I don't really want to cut out a whole bunch of that to get it to work, since it'll make maintaining it pretty hard. I might see if I can do some stuff with compile flags to just not include the problematic stuff automatically.

mildwood commented on 2017-09-11 17:46 (UTC)

@Pandoras_Fox That would be very nice, thanks a lot :) I tried again but without sucess, don't have time to tinker with it. Looking forward to it:)

Pandoras_Fox commented on 2017-08-08 12:51 (UTC)

@mildwood I actually have a raspberry pi now, so when I get back to college I'll look into making an arm-compat branch

Alad commented on 2017-06-09 00:48 (UTC)

Ask upstream, this is irrelevant to this package which only supports x86 architectures.

mildwood commented on 2017-06-03 13:31 (UTC)

Can someone help me out? How can i compile this for arch armv7h(raspberry 3)? The old i3lock-color works but this new one(after 2016-mid or so) does not. It needs intel compiler library and -msse2 even if i change architecture to armv7h. Thanks!

brandon099 commented on 2016-10-25 23:25 (UTC)

Thanks for the notifcation Dimtree! I've updated the package pulling in all of the upstream changes, including the MANDIR removal from package().

Pandoras_Fox commented on 2016-10-14 14:51 (UTC) (edited on 2016-10-14 14:54 (UTC) by Pandoras_Fox)

I never realized there was an AUR package for this (I'dve done it myself when I made the fork, but I never got around to it), so if there's anything I can do to make the package more seamless, let me know. Also, my bad about the binary name last spring. That was a poor choice I made at like 2am. I dunno why I did that.

brandon099 commented on 2016-03-29 21:31 (UTC)

@meskarune, thanks for the heads up for the upstream bug fix. I've added it to the PKGBUILD file. Thanks!

meskarune commented on 2016-03-28 12:26 (UTC)

Hello, in build() just before "make" the following needs to be added to fix an upstream bug with i3lock: sed -i -e 's:login:system-auth:' i3lock.pam Have a look at the Arch Linux i3lock package, they do the same thing. cheers and thanks for the quick package update \o

brandon099 commented on 2016-03-28 04:01 (UTC)

Updated to include @meskarune's Pull Request upstream to fix the binary name. Thanks!

parkerlreed commented on 2016-03-28 02:52 (UTC)

-> Cloning i3lock-color git repo... Cloning into bare repository '/tmp/packerbuild-1000/i3lock-color-git/i3lock-color-git/i3lock-color'... remote: Counting objects: 861, done. remote: Compressing objects: 100% (4/4), done. remote: Total 861 (delta 0), reused 0 (delta 0), pack-reused 857 Receiving objects: 100% (861/861), 226.49 KiB | 0 bytes/s, done. Resolving deltas: 100% (549/549), done. Checking connectivity... done. ==> Validating source files with md5sums... i3lock-color ... Skipped ==> Extracting sources... -> Creating working copy of i3lock-color git repo... Cloning into 'i3lock-color'... done. ==> Starting prepare()... ==> Starting pkgver()... ==> Updated version: i3lock-color-git r234.b2c3247-1 ==> Starting build()... cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -std=c99 -pipe -Wall -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libdrm -I/usr/include/libpng16 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -DVERSION=\""2.7-27-gb2c3247 (2016-03-27)"\" -c -o xinerama.o xinerama.c cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -std=c99 -pipe -Wall -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libdrm -I/usr/include/libpng16 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -DVERSION=\""2.7-27-gb2c3247 (2016-03-27)"\" -c -o xcb.o xcb.c cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -std=c99 -pipe -Wall -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libdrm -I/usr/include/libpng16 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -DVERSION=\""2.7-27-gb2c3247 (2016-03-27)"\" -c -o i3lock.o i3lock.c cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -std=c99 -pipe -Wall -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libdrm -I/usr/include/libpng16 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -DVERSION=\""2.7-27-gb2c3247 (2016-03-27)"\" -c -o unlock_indicator.o unlock_indicator.c cc -Wl,-O1,--sort-common,--as-needed,-z,relro -o i3lock xinerama.o xcb.o i3lock.o unlock_indicator.o -lcairo -lxcb-dpms -lxcb-xinerama -lxcb-util -lxcb-image -lxcb-shm -lxcb-xkb -lxcb -lxkbcommon-x11 -lxkbcommon -lpam -lev -lm ==> Entering fakeroot environment... ==> Starting package()... install -d /tmp/packerbuild-1000/i3lock-color-git/i3lock-color-git/pkg/i3lock-color-git/usr/bin install -d /tmp/packerbuild-1000/i3lock-color-git/i3lock-color-git/pkg/i3lock-color-git/etc/pam.d install -m 755 i3lock /tmp/packerbuild-1000/i3lock-color-git/i3lock-color-git/pkg/i3lock-color-git/usr/bin/i3lock install -m 644 i3lock.pam /tmp/packerbuild-1000/i3lock-color-git/i3lock-color-git/pkg/i3lock-color-git/etc/pam.d/i3lock gzip -kf i3lock.1 install -m 644 i3lock.1.gz /tmp/packerbuild-1000/i3lock-color-git/i3lock-color-git/pkg/i3lock-color-git/usr/share/man/man1/i3lock.1.gz install: cannot create regular file '/tmp/packerbuild-1000/i3lock-color-git/i3lock-color-git/pkg/i3lock-color-git/usr/share/man/man1/i3lock.1.gz': No such file or directory Makefile:40: recipe for target 'install' failed make: *** [install] Error 1

meskarune commented on 2016-03-28 02:26 (UTC)

Upstream fixed the issue with the binary having the incorrect name, but now all instances of "i3lock-color" in build and package need to be changed to "i3lock"

meskarune commented on 2016-03-27 16:32 (UTC)

This package appears to create a binary called "i3lock-color" instead of creating a binary called "i3lock". It would be fantastic if that could be fixed. Thanks.

meskarune commented on 2016-03-26 17:40 (UTC) (edited on 2016-03-26 17:49 (UTC) by meskarune)

Hello, I am running into this issue: The fix is to add this to build() just before make: sed -i -e 's:login:system-auth:' i3lock-color.pam cheers

brandon099 commented on 2016-03-14 23:21 (UTC)

I've updated this package to include libxkbcommon-x11 and it builds in a clean chroot now. Thanks!

maikoool commented on 2016-03-14 13:46 (UTC)

Building this in a clean chroot gives me the following error: Package xkbcommon was not found in the pkg-config search path. Perhaps you should add the directory containing `xkbcommon.pc' to the PKG_CONFIG_PATH environment variable No package 'xkbcommon' found Package xkbcommon-x11 was not found in the pkg-config search path. Perhaps you should add the directory containing `xkbcommon-x11.pc' to the PKG_CONFIG_PATH environment variable No package 'xkbcommon-x11' found Perhaps libxkbcommon-x11 needs to be added as a build time dependency?

parkerlreed commented on 2016-03-09 03:53 (UTC)

Cheers that worked.

brandon099 commented on 2016-03-07 15:38 (UTC)

It was building/installing with Pacaur (albeit with warnings), but it sounds like Packer stopped hard. PKGBUILD has been fixed to remove duplicate install of the Man pages to the pkgdir. Now everything should be happy -- sorry about that.

Moviuro commented on 2016-03-07 09:01 (UTC)

@parkerlreed because of L25 This causes along with L35 to install man pages to "$pkgdir/${pkgdir}/usr/share/man". Remove L25 to fix.

parkerlreed commented on 2016-03-05 20:03 (UTC)

error: failed to commit transaction (conflicting files) i3lock-color-git: /tmp/packerbuild-1000/i3lock-color-git/i3lock-color-git/pkg/i3lock-color-git/usr/share/man/man1/i3lock-color.1.gz exists in filesystem Why is the built package trying to install a file to /tmp?

brandon099 commented on 2016-03-04 18:26 (UTC) (edited on 2016-03-04 18:26 (UTC) by brandon099)

PKGBUILD fixed -- thanks! I'd also like to note that the binary has been renamed. It's now moved to /usr/bin/i3lock-color.

Moviuro commented on 2016-03-04 16:33 (UTC)

A better fix IMO: - make DESTDIR="$pkgdir" install + make MANDIR=${pkgdir}/usr/share/man/man1/ DESTDIR="$pkgdir" install

benjarobin commented on 2016-03-04 10:36 (UTC)

A quick fix :