Arch Linux

New version, tagged 1.0, removes that feature, so that it remains "simple", unix-like :P

Newer versions of slock seem to already use DPMS anyway:

if(len == 0 && DPMSCapable(dpy)) {
DPMSEnable(dpy);
DPMSForceLevel(dpy, DPMSModeOff);
}

(from slock-0.9)

I called myself dumb, I wasn't assuming you regarded me as such, though it's perfectly in place! :P
No offense taken whatsoever, that is a really stupid mistake... And it indeed will easily cause a segfault in i686 as well in x86_64.

I would guess no one was (should be) using this, though! It is easy to solve, but that code is not very polished anyway. I stopped using this because, with my new laptop, setting DPMS programmatically seems to be problematic...

Did not mean to offense you btw, was just a bit alarmed after discovering this :P . Also, the segfault only happened in lockx compiled for x86_64 so far, but I'm pretty sure that with enough backspace presses it could happen with the i686 version too (enough to make buffer[len] go below the top of the stack.

I am the dumb dev, and I agree with delroth, twice. First because there is a bug, in fact, and also beucase I no longer use/mantain this program!

Anyone who cares about the security of their locked session should not use this software. Simply press backspace, then any key. Boom, lockx segfaults.

This happens because the author of lockx does not seem to compile his software with warnings enabled. gcc easily detects that "--len < 0" is always false when "len" is an unsigned int.

Please use slock or xtrlock instead of this program.