command-not-found not working properly in karmic
Bug #420161 reported by
Michael B. Trausch
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:~$ asdfasdfasdfasf
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.
Related branches
Changed in command-not-found (Ubuntu): | |
importance: | Undecided → Medium |
status: | Confirmed → In Progress |
To post a comment you must log in.
Michael I am unable to reproduce the bug. Which version are you using, can try the latest package command-not-found
(0.2.37ubuntu3).