You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 18, 2026. It is now read-only.
It "works" in the sense that using my shortcut indeed runs xsecurelock before calling suspend.
However if I do something as simple as holding the left button of my mouse while using the shortcut, the pc is put to suspend, but when resuming, xsecurelock is not runing and anyone can access my desktop.
I thought that using --transfer-sleep-lock specifically handled this issue and cancelled suspend if xsecurelock was not able to grab the pointer.
My version of xss-lock is 0.3.0 and my version of xsecurelock is 1.9.0
Is there something wrong with my configuration?
As it is it is not secure at all...
Hello
I am using i3 and have the following configuration:
It "works" in the sense that using my shortcut indeed runs xsecurelock before calling suspend.
However if I do something as simple as holding the left button of my mouse while using the shortcut, the pc is put to suspend, but when resuming, xsecurelock is not runing and anyone can access my desktop.
I thought that using --transfer-sleep-lock specifically handled this issue and cancelled suspend if xsecurelock was not able to grab the pointer.
My version of xss-lock is 0.3.0 and my version of xsecurelock is 1.9.0
Is there something wrong with my configuration?
As it is it is not secure at all...