Hi! Finally I managed to build an unofficial knights package which should give an insight of the problem you reported (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305832).
My idea is that this is not a bug, since chess programs are very CPU hungry, and the "lockup" you experienced was nothing but gnuchess (or similar) doing its duty. In order to verify if this is true, please add the line deb http://people.debian.org/~moronito/unofficial/ binary/ to your sources.list and upgrade knights to version 0.6-4. Then run knights and the menu: settings -> Configure Knights -> Computer Opponents. Here select the chess engine your're going to use and click "modify", then specify a log file. Finally start a new game and look at the logfile; even when knights seems locked up, there should be some kind of activity in the logfile, showing that the chess engine is actually doing something! As usual, feel free to ask me clarifications. Regards, -- Tommaso Moroni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
