Bug#450717: libterm-readkey-perl: Call to ReadKey(0) is not blocking anymore

2007-11-13 Thread Michael Gebetsroither
Quoting Niko Tyni <[EMAIL PROTECTED]>: the child process is probably setting O_NONBLOCK on STDIN. Does it help if you do something like indeed, startx/Xorg seems to set O_NONBLOCK on the console where it sends the output to. use Fcntl qw(F_GETFL F_SETFL O_NONBLOCK); $flags = fcntl(STDI

Bug#450717: libterm-readkey-perl: Call to ReadKey(0) is not blocking anymore

2007-11-10 Thread Niko Tyni
On Fri, Nov 09, 2007 at 04:41:22PM +0100, Michael Gebetsroither wrote: > Package: libterm-readkey-perl > Version: 2.30-3 > Severity: normal > while (not defined ($x = ReadKey(0))) {} > > The real problem is, that after starting start-x and returning, the cpu > runs at 100% because ReadKey does no

Bug#450717: libterm-readkey-perl: Call to ReadKey(0) is not blocking anymore

2007-11-09 Thread Michael Gebetsroither
Package: libterm-readkey-perl Version: 2.30-3 Severity: normal Hi, We've a problem with ReadKey(0). We use it in one of our wrapper programms to read non-echoed single character's. Something like this: while (not defined ($x = ReadKey(0))) {} The real problem is, that after starting start-x an