On 2018-09-21, Ken M <k...@mack-z.com> wrote: > On Thu, Sep 20, 2018 at 08:20:18PM -0900, Philip Guenther wrote: >> 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 > > So below is what I did and that reveals a bit more. > > $ xscreensaver-command -exit > xscreensaver-command: exiting. > > $ ps aux|grep xscreen > me 73706 0.0 0.0 308 1348 p1 S+p 6:48AM 0:00.01 grep xscreen > $ xscreensaver && >> xscreensaver-command -lock > xscreensaver: 06:48:31: couldn't get password of "me" > xscreensaver: 06:48:31: couldn't get password of "root" > xscreensaver: 06:48:31: locking is disabled (error getting password). > xscreensaver: 06:48:31: does xscreensaver need to be setuid? consult the > manual. > >
Given the permissions you showed, the most likely reason would be if /usr/local is mounted with the "nosuid" flag.
