command-not-found is unusable after upgrade

[Alex V Breger]

Package: command-not-found
Version: 0.2.8ubuntu1
Severity: grave
Justification: renders package unusable

After upgrade command-not-found does not work
Bash does aclively forking and trys to get file "command-not-found" anywhere in PATH
It even able to kill my system

Why there is just command-not-found in /etc/bash_command_not_found ?
command_not_found_handle() {
  command-not-found -- "$1" || return 127
}

this file is at /usr/lib:
$ dpkg -L command-not-found
....
/usr/lib/command-not-found
....

So bash is recursively trying to start command-not-found... 


-- System Information:
Debian Release: lenny/sid
  APT prefers gutsy-updates
  APT policy: (500, 'gutsy-updates'), (500, 'gutsy')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-12-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages command-not-found depends on:
ii  command-not-found-data    0.2.8ubuntu1   Set of data files for command-not-
ii  python                    2.5.1-1ubuntu2 An interactive high-level object-o
ii  python-apt                0.7.3.1ubuntu2 Python interface to libapt-pkg
ii  python-central            0.5.15ubuntu2  register and build utility for Pyt

command-not-found recommends no packages.

-- no debconf information