This could be a corner case. I write a incorrect command on terminal when I have a high cpu load. As result meanwhile the command-not-found it is executed I have time to abort with Ctrl+C keys. So I think that the crash it is triggered by that.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: command-not-found 0.3ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic i686
ApportVersion: 2.2.5-0ubuntu2
Architecture: i386
Date: Sun Jul 8 07:13:01 2012
ExecutablePath: /usr/lib/command-not-found
InstallationMedia:
InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/lib/command-not-found -- teamviewersudo
ProcEnviron:
SHELL=/bin/bash
TERM=linux
PATH=(custom, no user)
LANG=es_ES.UTF-8
Signal: 6
SourcePackage: command-not-found
StacktraceTop:
Py_FatalError ()
Py_InitializeEx ()
Py_Initialize ()
Py_Main ()
main ()
Title: command-not-found crashed with SIGABRT in Py_FatalError()
UpgradeStatus: Upgraded to quantal on 2012-06-05 (32 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape vboxusers video
StacktraceTop:
Py_FatalError ()
Py_InitializeEx ()
Py_Initialize ()
Py_Main ()
main ()