Hi,
I cannot reproduce the problem :-( But, I cannot understand the behaviour. 1. xautolock calls vlock. xautolock waits vlock to unlock the screen. 2. vlock (shell script) calls vlock-main When vlock-main finish (the user enter the right passwd), then, and only then, xautolock should unlock the screen. How can xautolock continue (unlock) if vlock-main is still running? This bug should need "+moreinfo". IMO we cannot solve the problem if we cannot reproduce it. Could you try to run xautolock in other files? (.xinitrc and launch startx, run from console,...), download the source and add some "printf"?, ... Probably you can run "gdb" with the "-p" option, to check what code is running. The important serverity is right, because could be a security hole (I don't like it, but is right). Cheers, kix Rodolfo García Peñas (kix) http://www.kix.es/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
