Using intrepid I'm getting the same problem. Looking at /usr/lib/command-not-found the top line is as follows:
#!/usr/bin/python -S The -S says don't import site.py on initialisation. Now it looks that site.py is necessary to got the path set up correctly to find the CommandNotFound module. If I do: python /usr/lib/command-not-found ls it works fine without an error. So the fix here is either to remove the -S from the script or to fix the python initialisation so that it sets the python path up ok in the case when site.py is not imported. -- "No module named CommandNotFound" https://bugs.launchpad.net/bugs/268945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
