Package: xautolock Version: 1:2.7-7.1 Severity: important xautolock does not work as advertised. It is 3 times slow. For example, the command "xautolock -time 1 <command>" should execute command after 1 minute, however, it only executes the command after 3 minutes. The same happens when time is 5, and I assume any other value; xautolock will triple the requested time.
Perhaps this bug should be upgraded to serious, or grave, because it is potentially a security hazard. Many people use xautolock to lock their computers after a specified timeout, and expect it to be locked after the timeout period. Here is a log which demonstrates the misbehavior of xautolock, and proves my point. I have added spaces between commands for clarity: w...@alpha:~$ cat tmp.sh #!/bin/sh date > ~/tmp.txt w...@alpha:~$ date && xautolock -time 1 -locker /home/wk/tmp.sh Tue Sep 8 20:38:14 PDT 2009 ^C w...@alpha:~$ cat tmp.txt Tue Sep 8 20:41:17 PDT 2009 w...@alpha:~$ date && xautolock -time 1 -locker /home/wk/tmp.sh Tue Sep 8 20:42:47 PDT 2009 ^C w...@alpha:~$ cat tmp.txt Tue Sep 8 20:45:51 PDT 2009 w...@alpha:~$ date && xautolock -time 5 -locker /home/wk/tmp.sh Tue Sep 8 20:47:18 PDT 2009 ^C w...@alpha:~$ cat tmp.txt Tue Sep 8 21:02:18 PDT 2009 -Brandon
signature.asc
Description: PGP signature
