AUR (en) - i3lock-color

Search Criteria

Package Details: i3lock-color 2.13.c.5-3

Git Clone URL:	https://aur.archlinux.org/i3lock-color.git (read-only, click to copy)
Package Base:	i3lock-color
Description:	The world's most popular non-default computer lockscreen.
Upstream URL:	https://github.com/Raymo111/i3lock-color
Keywords:	i3 i3lock i3wm lock lockscreen
Licenses:	MIT
Conflicts:	i3lock, i3lock-color-git
Provides:	i3lock, i3lock-color
Submitter:	Alad
Maintainer:	Raymo111 (wilssonmartee)
Last Packager:	Raymo111
Votes:	59
Popularity:	0.96
First Submitted:	2020-10-18 21:53 (UTC)
Last Updated:	2024-08-29 00:57 (UTC)

Git Clone URL:

https://aur.archlinux.org/i3lock-color.git (read-only, click to copy)

Package Base:

i3lock-color

Description:

The world's most popular non-default computer lockscreen.

Upstream URL:

https://github.com/Raymo111/i3lock-color

Keywords:

i3 i3lock i3wm lock lockscreen

Licenses:

MIT

Conflicts:

i3lock, i3lock-color-git

Provides:

i3lock, i3lock-color

Submitter:

Alad

Maintainer:

Raymo111 (wilssonmartee)

Last Packager:

Raymo111

Votes:

Popularity:

0.96

First Submitted:

2020-10-18 21:53 (UTC)

Last Updated:

2024-08-29 00:57 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

Raymo111 commented on 2021-06-04 03:27 (UTC)

@hicklemon try updating to a newer version of betterlockscreen?

sysfs commented on 2021-06-04 03:04 (UTC)

This recent update seems to have broken my use of i3lock-color with betterlockscreen.

I'm now getting:

$ betterlockscreen -l dimblur Got 3840x2160 /home/mike/.cache/i3lock/3840x2160 i3lock: unrecognized option '--timepos=x+110:h-70' i3lock: Syntax: i3lock [-v] [-n] [-b] [-d] [-c color] [-u] [-p win|default] [-i image.png] [-t] [-e] [-f] Please see the manpage for a full list of arguments.

Seeing this issue here (from 2018!): https://github.com/pavanjadhaw/betterlockscreen/issues/29

I didn't change anything, so I'm wondering if there's something I should do.

Raymo111 commented on 2021-02-16 00:39 (UTC)

Thanks @wilssonmartee!

dreeg_ocedam commented on 2021-01-03 18:01 (UTC)

@wilssonmartee indeed, my bad. It's weird that I didn't have it installed on this computer. Sorry to have bothered you.

wilssonmartee commented on 2021-01-03 17:54 (UTC) (edited on 2021-01-03 17:57 (UTC) by wilssonmartee)

@dreeg_oced automake is part of base-devel, to start using AUR you need to have all the packages belonging to this group already installed so it would not be necessary to include it in makedepend. Source: https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

dreeg_ocedam commented on 2021-01-03 17:28 (UTC)

Indeed, after searching for a bit, it seems that automake was the missing build dependency. It should probably be added in the PKGBUILD.

Raymo111 commented on 2021-01-02 17:27 (UTC) (edited on 2021-01-02 17:27 (UTC) by Raymo111)

@dreeg_ocedam do you have autoconf installed? You should install the whole build-devel group to build packages.

dreeg_ocedam commented on 2021-01-01 19:49 (UTC)

Hello, since the last update, I get the following error in the build function:

Can't exec "aclocal": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 274.
autoreconf: error: aclocal failed with exit status: 2

Raymo111 commented on 2020-12-23 20:07 (UTC) (edited on 2020-12-23 20:07 (UTC) by Raymo111)

@tortenairbag You need to install autoconf, which is in base-devel, before building AUR packages.

tortenairbag commented on 2020-12-23 11:34 (UTC)

Hi everyone, I get an error updating this package from 2.12.c.5-1 to 2.13.c.1-1

~/.cache/yay/i3lock-color/PKGBUILD: line 21: autoreconf: command not found

The package "autoconf" is missing as build dependency