Page MenuHomeSolus

Switch (back) to i3lock-color fork
Open, Needs More InfoPublic

Description

A while back the i3lock repo was switched to the i3lock-color fork but quickly reverted back to the standard version due to stability issues with the fork. (See our i3lock repo for the history on this.)

I've been using the i3lock-color fork for a few months, locally built on my Solus machine.

Can we consider moving (again) to this fork? I can do the work if needed.

Event Timeline

JoshStrobl triaged this task as Wishlist priority.Oct 15 2019, 1:09 AM
JoshStrobl moved this task from Backlog to Improvement on the Software board.
JoshStrobl added a subscriber: JoshStrobl.

I'll consider it when they're properly rebased, with a new release, against i3lock 2.12 (note that i3lock-color 2.12 is not the same as i3lock 2.12). Until then, no.

DataDrake raised the priority of this task from Wishlist to Needs More Info.Mar 13 2022, 1:35 AM
DataDrake added a subscriber: DataDrake.

Seems like i3lock-color is more actively maintained than i3lock these days. I'd be interested to get some fresh takes on this change.