Hi, probably I'm just dense, but why would (the admittedly gross hack) of looking at /proc/$XSCREENSAVER-PID/environ (for DISPLAY and XAUTHORITY), getting uid for that process, trying xscreensaver-command -exit, if the screensaver exited, start xscreensaver again with that uid and environ, otherwise (it will have been locked) killing the xscreensaver, starting xscreensaver, doing xscreensaver-command -lock not do the trick better than the current state?
Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
