command-not-found not working properly in karmic

Bug #420161 reported by Michael B. Trausch
34
This bug affects 10 people
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

When typing an invalid command name, I expect an error, but I do not get one unless the database has alternatives:

mbt@zest:~$ afsdasdfasdfasdf
mbt@zest:~$ asdfasdfasdfasfajsgfahghags
mbt@zest:~$ echo $?
127
mbt@zest:~$ lsls
No command 'lsls' found, did you mean:
 Command 'lslk' from package 'lslk' (universe)
mbt@zest:~$ ldld
No command 'ldld' found, did you mean:
 Command 'ldd' from package 'libc6' (main)
 Command 'tdld' from package 'tdl' (universe)
mbt@zest:~$ echo $?
127
mbt@zest:~$

This is in a just-updated Karmic install.

Revision history for this message
arky (arky) wrote :

Michael I am unable to reproduce the bug. Which version are you using, can try the latest package command-not-found
 (0.2.37ubuntu3).

affects: ubuntu → command-not-found (Ubuntu)
Changed in command-not-found (Ubuntu):
status: New → Incomplete
Revision history for this message
Michael B. Trausch (mtrausch) wrote :

mbt@zest:~$ dpkg -l bash command-not-found
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii bash 4.0-4ubuntu1 The GNU Bourne Again SHell
ii command-not-fo 0.2.37ubuntu3 Suggest installation of packages in interact

It *is* a problem:

mbt@zest:~$ asdfasdfasdf
mbt@zest:~$ echo $?
127
mbt@zest:~$ lsls
No command 'lsls' found, did you mean:
 Command 'lslk' from package 'lslk' (universe)
mbt@zest:~$ lslslslslslslsls
mbt@zest:~$ echo $?
127
mbt@zest:~$

At this time there are no available updates for my system (I just did an apt-get update followed by a dist-upgrade).

Changed in command-not-found (Ubuntu):
status: Incomplete → New
Revision history for this message
Michael B. Trausch (mtrausch) wrote :

I just created a new stock user account, and the same thing happened there as well. If an SSH account would help to troubleshoot, I will happily make one provided that a public key is provided (no password).

Revision history for this message
Id2ndR (id2ndr) wrote :

Confirmed here. Karmic install since alpha4 and up-to-date.

Revision history for this message
Michael B. Trausch (mtrausch) wrote :

Updating status to confirmed, as it has been confirmed by another user.

Changed in command-not-found (Ubuntu):
status: New → Confirmed
Michael Vogt (mvo)
Changed in command-not-found (Ubuntu):
importance: Undecided → Medium
status: Confirmed → In Progress
Revision history for this message
Michael Vogt (mvo) wrote :

I just checked and this seems to be caused by the new bash-4.0 release.

Revision history for this message
Michael Vogt (mvo) wrote :

So it seems that the behaviour of the shell changed and it does no longer print a error message itself. I will let command-not-found print one.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
command-not-found (0.2.38ubuntu1) karmic; urgency=low

  * updated data to current karmic
  * print error if a command is not found (bash used to do that
    but with bash-4.0 it does no longer) LP: #420161

 -- Michael Vogt <email address hidden> Wed, 02 Sep 2009 16:13:17 +0200

Changed in command-not-found (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Michael B. Trausch (mtrausch) wrote : Re: [Bug 420161] Re: command-not-found not working properly in karmic

On Wed, 2009-09-02 at 14:49 +0000, Michael Vogt wrote:
> So it seems that the behaviour of the shell changed and it does no
> longer print a error message itself. I will let command-not-found print
> one.

Was that by design, or does someone need to file a bug upstream?

I'm thinking a bug... no news is good news, not the inverse...

 --- MIke

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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