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

[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 and returning, the cpu
runs at 100% because ReadKey does not block anymore and returnes
undefined value all of the time.

Code which shows this behaviour:
http://hg.grml.org/grml-scripts/file/84f9e6d8cda1/usr_sbin/grml-quickconfig

cu,
michael

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (991, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-grml64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.iso885915, LC_CTYPE=en_US.iso885915 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages libterm-readkey-perl depends on:
ii  libc6                         2.6.1-6    GNU C Library: Shared libraries
ii  perl                          5.8.8-11.1 Larry Wall's Practical Extraction 
ii  perl-base [perlapi-5.8.8]     5.8.8-11.1 The Pathologically Eclectic Rubbis

libterm-readkey-perl recommends no packages.

-- no debconf information