[SOLVED] [i3wm] xss-lock not working properly with systemd suspend

ld_40 · 2024-07-12 17:27:16

So I recently made a switch to i3 since I prefer the workflow of i3 to KDE and I was configuring my setup. However the default:

exec --no-startup-id xss-lock --transfer-sleep-lock -- i3lock --nofork

Simply does not work the way it should or all the time. For starters, I have seen that the way it should work is that once systemctl is called either by detecting a certain amount of idle time or manually xss-lock will transfer it over to i3lock to first lock the screen and then suspend the machine. In action I have seen i3 starts off by showing to the user that it is locking the screen and then it suspends. However on my end, it happens quite fast and the main problem arises. It does suspend but when I return to using it and it wakes up from suspend, it refuses to accept the first password. It takes a while saying "Verifying..." but always returns verifying failed. This happens regardless if the password I entered was correct. I also have noticed that it returns from suspend with the green circle every time.

I have been trying to find out why this has been happening and have not really found anything that can solve it. I checked the arch wiki for i3 and the arch wiki regarding https://wiki.archlinux.org/title/Power_ … temd_units and still have not really found what it is that is causing this. I am not sure what it is exactly I should probe to see signs of errors either.

But what really irritates me in trying to figure the situation out, is that this is happening off and on. That is, sometimes, xss-lock is working fine and after waking from suspend, i3lock does not present this issue. But sometimes, I experience the issue I described earlier. I cannot tell at this point if there is an execution race occurring between xss-lock and systemd's suspend.

Any and all help would be appreciated.

Last edited by ld_40 (2024-07-13 00:49:08)

seth · 2024-07-12 20:49:20

The only problem is the failing password?

setxkbmap -print -query
localectl status

https://wiki.archlinux.org/title/Xorg/K … tion_files

What might happen is that you've a non-qwerty keybaord, configure a transient layout (running setxkbmap somewhen) and the keyboard logically re-attaches w/ the suspend, resulting in the layout being reset to qwerty

ld_40 · 2024-07-13 00:48:32

You are correct that it was only my password failing but with that in mind, you actually helped me solve it. So I didn't think it could be the case but I had installed some other keyboards to use since I have to use other keyboards (specifically german, hangul, and spanish), and I went ahead to just keep qwerty on my system. And, then, I tested i3lock. It was consistently working now. I do not know why having my other keyboards was a problem. I assume something with my personal configuration on my system otherwise I doubt this issue is a common issue. Thanks for the insight! I will probably reinstall the keyboards I was using later but I have to figure out how to make my setup properly use the correct keyboards when I am entering the password.

Arch Linux

#1 2024-07-12 17:27:16

[SOLVED] [i3wm] xss-lock not working properly with systemd suspend

#2 2024-07-12 20:49:20

Re: [SOLVED] [i3wm] xss-lock not working properly with systemd suspend

#3 2024-07-13 00:48:32

Re: [SOLVED] [i3wm] xss-lock not working properly with systemd suspend

Board footer