[Bug 348011] [NEW] In init. after init-bottom, start-up comes to dead-end at module CommandNotFound

[Paul Gabrielsson]

Public bug reported:

Binary package hint: command-not-found

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 CommandNotFound
Traceback (most recent call last):
  File "/usr/lib/command-not-found", line 10, in <module>
    from CommandNotFound import CommandNotFound
ImportError: No module named CommandNotFound
Python version: 2.5.1 final 0

Comment: Problem arises during start up of the system, after init-
bottom, module CommandNotFound reports that module CommandNot Found
doesn´t exist (of course, when init is implemented so that any, given
module, is requested to import the very same module, it will be like a
never-ending ring, round and round we go...)

** Affects: command-not-found (Ubuntu)
     Importance: Undecided
         Status: New

-- 
In init. after init-bottom, start-up comes to dead-end at module CommandNotFound
https://bugs.launchpad.net/bugs/348011
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs