Update: Actually I can confirm that on systems where the "setting locale
failed" problem appears also command-not-found is broken and crashes as
reported by Martin here. When you get rid of the "setting locale failed"
problem, command-not-found does not crash anymore.
But nevertheless, even if the locale cannot be set correctly command-
not-found should not crash but give a hint to the problem like i.e.
"perl" does:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_PAPER = "a4",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937714
Title:
command-not-found crashing with incomplete locale settings
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/937714/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
