Well, that eliminates the processor variable. I don't think it's the testing libc6-i686 either -- I've tried this on some testing machines and they work just fine, and nothing in the changelog suggests that it would impact this bug.
It looks to me like the problem is that the input thread isn't being restarted. Either that, or that curses isn't reinitializing the terminal for some reason, but the code to bring curses back up is 'obviously right' and hasn't changed recently, whereas the input thread was rewritten recently. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
