*** This bug is a duplicate of bug 174305 ***
https://bugs.launchpad.net/bugs/174305
Public bug reported:
While debootstrappig an hardy chroot, I installed command-not-found
inside.
But it didn't work as exepcted:
$ foo
KABOOOM!!!
Whoops, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/ubuntu/+source/command-not-found
Please include the following information with the report:
No module named gdbm
Traceback (most recent call last):
File "/usr/lib/command-not-found", line 10, in <module>
from CommandNotFound import CommandNotFound
File "/usr/lib/python2.5/site-packages/CommandNotFound/__init__.py", line 1,
in <module>
from CommandNotFound import CommandNotFound
File "/usr/lib/python2.5/site-packages/CommandNotFound/CommandNotFound.py",
line 4, in <module>
import sys, os, os.path, gdbm, posix, grp
ImportError: No module named gdbm
Python version: 2.5.1 final 0
bash: foo: command not found
An "apt-get install python-gdbm" solves the issue.
** Affects: command-not-found
Importance: Undecided
Status: New
--
Should require python-gdbm
https://bugs.launchpad.net/bugs/174891
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu (via bug 174305).
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
