Package Details: swaylock-effects 1.7.0.0-4

Git Clone URL: https://aur.archlinux.org/swaylock-effects.git (read-only, click to copy)
Package Base: swaylock-effects
Description: A fancier screen locker for Wayland.
Upstream URL: https://github.com/jirutka/swaylock-effects
Licenses: MIT
Conflicts: swaylock
Provides: swaylock
Submitter: itsme
Maintainer: prokoprandacek
Last Packager: itsme
Votes: 39
Popularity: 2.16
First Submitted: 2021-01-31 13:39 (UTC)
Last Updated: 2026-03-16 08:44 (UTC)

Required by (37)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

itsme commented on 2026-03-29 20:29 (UTC)

I passed on maintaining this package to prokoprandacek.

Naeth commented on 2026-03-21 10:57 (UTC)

@itsme, no worries, mistakes happen. Thanks for reverting and definitely thanks for the effort of maintaining the package so far!

prokoprandacek commented on 2026-03-17 19:35 (UTC)

Thanks for reverting. I am willing to maintain this if you want to get rid of this.

itsme commented on 2026-03-16 08:50 (UTC)

I have reverted the package to jirutka's repository. A manual rebuild is mandatory for all users.

I apologize for not being cautious enough; I’ve been short on time recently and didn't give the update the attention it required.

Is anyone interested in taking over as the maintainer for this package?

lae commented on 2026-03-11 14:51 (UTC) (edited on 2026-03-19 17:32 (UTC) by lae)

I was unable to find any discussion that would attract users to their fork so the quick turnaround time from the emergence of their fork to this update seems suspicious. Their fork also contains commits that smell of AI-generated work, namely the "code audit" that without any further context seems reactionary to how Hans's PR was handled.

fwiw I've put this package in my IgnorePkgs until I can get a better handle on how trustworthy the updated upstream is.

Naeth commented on 2026-03-11 07:59 (UTC)

Yeah, jirutka isn't a very active maintainer. They apparently lack the time. However, they are a diligent one, and take the task very seriously.

I feel uneasy about relying on the hboetes repository. The unnecessarily rude attitude, squashing other people's PRs into their own, having a pretty major bug in important software? None of this screams "stable maintainer" to me.

itsme commented on 2026-03-11 06:55 (UTC)

@Naeth, I need to think about it. Something can probably be done with the bug.

itsme commented on 2026-03-11 06:49 (UTC)

jirutka's repository seems completely abandoned to me. There are no commits or releases in more than 3 years. I also want to mention that not only the fingerprint feature was added in hboetes' repository: https://github.com/hboetes/swaylock-effects/commits/master/. And I personally need the fingerprint feature. Anyway, could you please explain to me why the patch needs to be applied to code from the dead repository?

Naeth commented on 2026-03-11 06:23 (UTC)

I second this. Please revert upstream to jirutka. Apparently, the hboetes fork contains a major bug: https://github.com/jirutka/swaylock-effects/pull/76#issuecomment-4034903552

prokoprandacek commented on 2026-03-10 22:18 (UTC)

Why is hboetes the new upstream? They have a bad vibe when trying to upstream their changes: https://github.com/jirutka/swaylock-effects/pull/76. "Please add them, ASAP. So annoying to see great PRs waiting for committing" is a red flag.

If the fingerprint feature is so important why don't you apply quantum5's patch over jirutka's upsteam? hboetes just took the patch and then was rude about it.

1 2 3 4 Next › Last »