On Thu, Sep 20, 2018 at 4:41 PM Ken M <k...@mack-z.com> wrote:
> I am following -current and use openbox if it matters for my window
> manager.
> xscreensaver is started by openbox, anyway when I try to lock, well this
> is what
> I see:
>
> $ xscreensaver-command -lock
> xscreensaver-command: locking not enabled.
>
If xscreensaver decides it can't do locking, then when started it should
write to stderr why it thinks that. Does openbox capture the stderr of the
processes that it starts to some file you can review? If not, then stop
xscreensaver with
xscreensaver-command -exit
and then start xscreensaver against manually in a shell and see what it
says.
Philip Guenther
