Package: xautolock
Version: 1:2.2-5.1+b1
Hello,
The locker executable passed with the "-locker" option may exit
non-zero if it fails to lock the display for some reason.
In this case, it seems that "xautolock -locknow" should also exit
non-zero, indicating that the lock operation failed. It should also
write the error to stderr. This would, in my opinion, be the
preferred behavior.
However, perhaps xautolock is designed to immediately accept the
"-locknow" command, and the non-zero exit code indicates that the
command was received. Even in this case, xautolock should write a
message to stderr so the problem can be logged to e.g.
~/.xsession-errors. Currently, xautolock does nothing, silently
failing to lock but never indicating this anywhere.
Similarly, a "-locknow" attempt after a "-disable" should exit
non-zero. For example:
```
$ xautolock -disable
$ xautolock -locknow # <-- This is ignored
$ echo $?
0
```
The "-locknow" command is silently ignored; it should exit non-zero.
See also bug 720362, which describes an alternative way to fix this.
Thanks.
