Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No longer being able to unlock the screen #296

Open
Samueru-sama opened this issue Feb 23, 2024 · 0 comments
Open

No longer being able to unlock the screen #296

Samueru-sama opened this issue Feb 23, 2024 · 0 comments

Comments

@Samueru-sama
Copy link

This issue is a....

[x ] Bug
[ ] Other kind of issue (Please describe in detail)

Current Behavior

I updated i3lock-color after having it used for about a year, I keep i3lock-color along with i3 in my '~/.local/bin' dir due to the fact that I run i3 with a patch and not from a official repo so I keep all the i3 stuff there.

To update I simply took the latest binary from release and put it on my ~/.local/bin dir.

After updating I could not unlock my screen, it constantly said that the password was wrong, I had to log to a different tty and kill i3lock.

Restoring the older binary I had from a backup fixed the issue.

If I take the binary from the release it doesn't work if I put it in either /usr/bin or ~/.local/bin, it locks the screen but fails to unlock when the password is given.

However if I install i3lock from the aur it does work, but moving the binary to ~/.local/bin makes it fail to unlock the screen again.

So only my older binary works, the aur package partially works, and the binary from release does not work.

Environment

i3lock version: 479ae5e

What's interesting is that the aur package and my older binary are both version 2.13.c.5, however they are not the same, only my older binary works, the binary is 128 KiB while the one from the aur package is 124 KiB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant