KeyboardInterrupt is not catched
Bug #479716 reported by
Matthias Klose
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/
import CommandNotFound
File "/usr/lib/
from CommandNotFound import CommandNotFound
File "/usr/lib/
import sys, os, os.path, gdbm, posix, grp, string
KeyboardInterrupt
Related branches
Changed in command-not-found (Ubuntu): | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
To post a comment you must log in.
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