You are not logged in.
- Topics: Active | Unanswered
#1 2023-04-18 01:07:05
- cherrynoize
- Member
- Registered: 2023-04-18
- Posts: 2
slock autodies after timeout
First post here on this forum, but I really can't figure this out or find this anywhere else.
The issue is exactly as described. After a certain (unmeasured, but I could say between 30s and 1 minute) lock time, slock automatically unlocks/dies and just disappears leaving the X session completely open and accessible.
I have found a slock fork mentioning DPMS settings, but I really don't think that's the point. I want slock to keep running, not my computer to suspend again.
How can I achieve that? Or any clue as to what the cause to this might be here?
Offline
#2 2023-04-18 07:09:22
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 77,063
Re: slock autodies after timeout
slock does not "automatically unlock", the process either crashes or gets killed.
Do you "AllowClosedownGrabs" ?
You could try to run lock in gdb, but DO NOT DO THAT FROM THE GUI SESSION. When slock crashes, gdb will halt it and you won't return to the session.
Move to another VT or ssh in, "export DISPLAY=:0" and run "gdb slock" there.
You could also use xephyr as testserver.
Though since it's hard to believe that the lean codebase of slock actually crashes, how exactly do you start slock?
Offline