Package Details: sxlock-git 2.0-1

Git Clone URL: https://aur.archlinux.org/sxlock-git.git (read-only, click to copy)
Package Base: sxlock-git
Description: Simple screen locker utility for X, fork of sflock. Uses PAM authentication, no suid needed.
Upstream URL: https://github.com/lahwaacz/sxlock
Licenses: MIT
Submitter: lahwaacz
Maintainer: lahwaacz
Last Packager: lahwaacz
Votes: 23
Popularity: 0.000000
First Submitted: 2013-02-23 15:02 (UTC)
Last Updated: 2022-03-19 12:32 (UTC)

Dependencies (6)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

lahwaacz commented on 2022-04-07 05:55 (UTC)

@sproot: This was already fixed in https://aur.archlinux.org/cgit/aur.git/commit/?h=sxlock-git&id=4e6578d3ba227b11aa90dde566cda70d94642608

sproott commented on 2022-04-06 22:14 (UTC) (edited on 2022-04-06 22:14 (UTC) by sproott)

I'm getting an error when building:

error: failed to lookup: sxlock-git: fatal: remote error:

The unauthenticated git protocol on port 9418 is no longer supported.

Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.

lmat commented on 2019-11-19 14:58 (UTC)

I did not. Now I have, and the error is solved.

Ah, I see that xorg-fonts-misc is an optional dependency, so I guess this makes sense. Thank you!

lahwaacz commented on 2019-11-18 22:05 (UTC)

@lmat: do you have xorg-fonts-misc installed?

lmat commented on 2019-11-18 22:01 (UTC)

sxlqck; says "sxlock: error: could not find font. Try using a full description." I don't have many fonts installed, so I'm guessing it wants one I don't have.

I see this was discussed at the end of 2018. Maybe the font requirement has changed?

Arkanosis commented on 2018-11-18 10:22 (UTC)

That was fast! Thanks a lot!

lahwaacz commented on 2018-11-18 08:26 (UTC)

Fixed, thanks.

Arkanosis commented on 2018-11-18 02:35 (UTC)

Hi! Thanks for having packaged sxlock :) Shouldn't xorg-font-misc come as optdepends, as sxlock's default font is absent from Arch without it? Thanks again!

kyak commented on 2015-10-11 17:39 (UTC)

Ah, thanks for answering! Indeed, it makes sense now...

lahwaacz commented on 2015-10-11 15:27 (UTC)

Hi kyak, I don't think it is generally useful because there is no way to let the service know which user is currently logged in. See https://github.com/lahwaacz/sxlock/issues/5#issuecomment-38022950