[12.04] command-not-found is showing a wrong version when its crashing

[Michael Basse]

michael@eeebuntu:~$ much .config/openbox/lxde-rc.xml
Sorry, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/command-not-found/+filebug
Please include the following information with the report:

command-not-found version: 0.2.44

---

michael@eeebuntu:~$ vii foo
Sorry, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/command-not-found/+filebug
Please include the following information with the report:

command-not-found version: 0.2.44

and so on

i tried to get more usefull infos with "strace vii foo" but that is not calling "command-not-found" :(

So if there are any actions to provide a better debug on that, please let me know

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: command-not-found 0.2.46ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Thu Feb 2 20:42:55 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=de
 SHELL=/bin/bash
SourcePackage: command-not-found
UpgradeStatus: Upgraded to precise on 2011-12-04 (60 days ago)

[Michael Basse (michael-alpha-unix)]

strange

Package: command-not-found 0.2.46ubuntu1

but the error-message is telling me command-not-found version: 0.2.44

[Michael Basse (michael-alpha-unix)]

other users reported me that they dont face the issue but i dont want to close the bug yet. I want to do some more debugging on that.

Maybe there a two bugs

 - the crash itself (only affecting me)
- a wrong version-output when its crashing (affecting all)

after some debug i will upate this bug, so please dont close it at the moment

[Michael Basse (michael-alpha-unix)]

as i thought

apt-get source command-not-found
...
...
michael@eeebuntu:~/ubuntu-dev/command-not-found-0.2.46ubuntu1$ grep 0.2.44 *
command-not-found:__version__ = "0.2.44"
setup.py: version='0.2.44',

[Michael Basse (michael-alpha-unix)]

i also found the reason for the crash from #1

michael@eeebuntu:~/ubuntu-dev/command-not-found-0.2.46ubuntu1$ vii foobar
Der Befehl »vii« wurde nicht gefunden, aber es gibt 19 ähnliche Befehle
vii: Befehl nicht gefunden.

michael@eeebuntu:~/ubuntu-dev/command-not-found-0.2.46ubuntu1$ LANG=en <------
michael@eeebuntu:~/ubuntu-dev/command-not-found-0.2.46ubuntu1$ vii foobar
Sorry, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/command-not-found/+filebug
Please include the following information with the report:

command-not-found version: 0.2.44

so its crashing when changing the language

[Michael Basse (michael-alpha-unix)]

its LANG=en_US.UTF-8 not LANG=en, so the crash was my fault but the version-bug is still there, i changed the bug-subject

[Michael Basse (michael-alpha-unix)]

before i just replace the version-string in it i guess it would be a good idea to have a look if the source in command-not-found-0.2.46ubuntu1 is really 0.2.46 so that just the version-number was not changed or if we are facing another bug like wrong source-code pulled into command-not-found-0.2.46ubuntu1

[chris (christian.ego)]

The problem seems to occur together with missing locales.
After generating utf-8 locales as described here: http://perlgeek.de/en/article/set-up-a-clean-utf8-environment command-not-found did not longer crashed.

[dvo (mueller8)]

The reason for the crash is indeed a locale setting that command-not-found cannot handle, e.g.
LC_CTYPE = "UTF-8" (which may be introduce, for example, via ssh from Mac OS X Lion).
Fixing the locale (e.g., unset LC_CTYPE) is a workaround,
but actually the instability in command-not-found causing the crash should be fixed.

[chris (christian.ego)]

confirmed. After changing the locale settings I had no more problems

[Raja Gopal Muralidharan (smrajagopal)]

Chris : You are absolutely right. The link you provided in the comment #8. Helped me .

Thanks,
Raj.

[Christopher Lee (clkrigbaum)]

I was having the same issue for a couple weeks till I did a search and found this forum.
All I did to fix was type in ... LANG=en_US.UTF-8 into a terminal as root exactly the way it is and this problem goes away.

[Joachim (joachimrs)]

Sorry, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/command-not-found/+filebug
Please include the following information with the report:

command-not-found version: 0.2.44

right after I did a apt-get update and apt-get upgrade and did the proposed

apt-get install linux-generic-lts-trusty linux-image-generic-lts-trusty

for extended support on 12.04