Ubuntu
command-not-found package

KeyboardInterrupt is not catched

Bug #479716 reported by Matthias Klose
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: command-not-found

when interrupting with ^C:

$ Traceback (most recent call last):
  File "/usr/lib/command-not-found", line 8, in <module>
    import CommandNotFound
  File "/usr/lib/python2.6/dist-packages/CommandNotFound/__init__.py", line 1, in <module>
    from CommandNotFound import CommandNotFound
  File "/usr/lib/python2.6/dist-packages/CommandNotFound/CommandNotFound.py", line 4, in <module>
    import sys, os, os.path, gdbm, posix, grp, string
KeyboardInterrupt

Michael Vogt (mvo)
Changed in command-not-found (Ubuntu):
status: New → Fix Committed
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package command-not-found - 0.2.40ubuntu1

---------------
command-not-found (0.2.40ubuntu1) lucid; urgency=low

  * scan.data:
    - updated to current lucid
  * command-not-found:
    - catch KeyboardInterrupt during initial import as
      well (LP: #479716)
    - show "command not found" string only when no command
      was found (LP: #408020)
 -- Michael Vogt <email address hidden> Mon, 11 Jan 2010 09:30:41 +0100

Changed in command-not-found (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.