Skip to content
This repository has been archived by the owner on Jan 13, 2019. It is now read-only.

various issues with i3lock-next #24

Open
cortex3 opened this issue Mar 22, 2018 · 2 comments
Open

various issues with i3lock-next #24

cortex3 opened this issue Mar 22, 2018 · 2 comments
Assignees
Labels

Comments

@cortex3
Copy link

cortex3 commented Mar 22, 2018

hi owen,
It's me again, just wanted to give you a heads up about a few issues im having. When trying to launch the freshly installed i3lock i get the following error
i3lock: unrecognized option '--time-font=Sans'
after editing it to --timefont=Sans i get the same issue for date-font. After editing that one too I get the error i3lock: unrecognized option '--verifcolor=00000000' after commenting that line out im finally able to launch i3lock-next but the locks and dates dont seem to be centered on my 2 monitors and after exiting I get a bunch of memory leaks. The memory leaks seem to be a problem from i3lock-color. I'd debug this issue further but im not much of a programmer and don't have enough time at the moment but feel free to ask me to test something for you. I'm aware that this is a rather small project and i don't expect this to be fixed anytime soon. In the meantime I'm gonna look for a new i3lock.

@owenthewizard
Copy link
Owner

I believe the issues you're experiencing were introduced in 4456c3a, which brought arguments passed to i3lock-color in line with upstream. Are you using the latest version of i3lock-color?

@cortex3
Copy link
Author

cortex3 commented Mar 23, 2018

I was using the latest i3lock-color version from the AUR. I changed to i3lock-color-git from the AUR which resolved all of the issues besides the lock placement and date placement.

@owenthewizard owenthewizard self-assigned this Mar 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants