Ubuntu
command-not-found package

  1. Bug #135327
  2. Comment #7

Comment 7 for bug 135327

Revision history for this message
Steve Illgen (sillgen) wrote : Re: [Bug 135327] Re: command-not-found Crashing

It works(!) now after I installed the latest patch fixes for Gutsy this
morning. The only problem is, I still get the "rc" status for
command-not-found with dpkg -l.

Here is the output:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
rc command-not-fo 0.2.7 Suggest installation of packages in
interact
ii command-not-fo 0.2.7 Set of data files for command-not-found.

On 8/29/07, dAniel hAhler <email address hidden> wrote:
>
> >From the output of "dpkg -l command-not-found" it seems like command-
> not-found is not installed after all? (status "rc").
>
> What does happen now, if you try to execute an unknown command?
>
> What's the output of
> set | grep -C 2 command-not-found
> ?
>
> --
> command-not-found Crashing
> https://bugs.launchpad.net/bugs/135327
> You received this bug notification because you are a direct subscriber
> of the bug.
>