Thinkpad x220 resume not locking screen

[bceverly]

Hi,

I'm running OpenBSD 5.7 and Gnome3 on my Thinkpad x220 and everything is working great with one small exception:

When I open my laptop after it has been suspended, the screen is not locked.

Is there something I need to configure to get this to lock on lid close so that when it opens I am prompted for my password just as if the screen locked normally via a timeout?

Thanks in advance.

[jggimi]

I do this with xidle(1) and apmd(8) scripts in /etc/apm, as articulated in the FILES section of that man page. The scripts use "pkill -USR1 xidle"

[bceverly]

Thanks for the suggestion. I looked at the apmd manpage and it was pretty clear. I created /etc/apm and put a file called "resume" in there with the following contents:

dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver \
org.gnome.ScreenSaver.Lock
echo "resuming..." >>/tmp/results.txt

I marked the file as executable and have verified that the dbus-send command does lock the screen. I can see that /tmp/results.txt is getting appended to so I know it's running. Any suggestions? I tried renaming the file to suspend and am getting the same results.

Sorry to be such a n00b. I'd be fine even with a way to configure Gnome to lock on resume from suspend. It just seems silly to have an encrypted drive and have opening the lid when I suspend take me right to the desktop.

[jggimi]

I have the following within the $HOME/{.xinitrc,.xsession} script. These are the same file, linked with ln(1) in the event I manually start X or use xdm(1).

xidle -delay 3 -sw -program "/usr/X11R6/bin/xlock -mode atunnels" &

Then, my /etc/apm/{suspend,standby,hibernate} script contains the pkill command, followed by a 2 second sleep(1).

pkill -USR1 xidle
sleep 2

I'm not using Gnome, just a simple tiling window manager.

[spiderpig]

Originally Posted by jggimi

Then, my /etc/apm/{suspend,standby,hibernate} script contains the pkill command, followed by a 2 second sleep(1).

pkill -USR1 xidle
sleep 2

I have a couple of questions...

1. What is the purpose of the sleep statement here?
2. Does this executable script need to have the following line at the top?
   

   #!/bin/sh

   Is this not necessary?

Thanks for the info!

[jggimi]

Both script fragments show in this thread were excerpts from longer scripts. I'm sorry if that added any confusion.

I used hash bangs (or, as Wikipedia calls them, shebangs) as these are executable shell scripts. Per apmd(8):

Each file must be an executable binary or shell script.

The two second delay was added because I discovered I needed it with the low power workstation where it is deployed. You may not require it.