On Tue, Sep 08, 2015 at 02:44:26PM +0100, Nick wrote: > Quoth Dimitris Papastamos: > > On Tue, Sep 08, 2015 at 02:30:39PM +0100, Nick wrote: > > > Separately to this, slock seems to exit (without prompt) after about > > > 0.3s after I run it, unless I move the mouse or hit the keyboard > > > directly after starting it. Has anyone else seen this? I could look > > > into it more, but wonder if I am perhaps being stupid? > > > > Please provide a backtrace. > > I looked into it a bit more, and it turns out it is exiting with > status 1; I double-checked and indeed it is returning from the > "nothing to protect" condition.
I am not sure why, can you try to increase the timeout in the two loops that grab the pointer/keyboard inside lockscreen()? I suspect len is 0 and lock is set to NULL.
