On Tue, Oct 7, 2014 at 5:20 PM, Ben Howard <email address hidden> wrote:
> Marking as confirmed, I can see this happen as well.
>
> ** Changed in: command-not-found
> Status: New => Confirmed
>
> ** Description changed:
>
> - When I SSH on to a pristine cloud instance, I see a crash:
> + command-not-found crashes when the LC_TYPE is defined in the environment
> + but is not installed. This can be seen via SSH which sets the LC_TYPE.
>
> $ env
> TERM=xterm
> SHELL=/bin/bash
> <snip>
> LANG=en_US.UTF-8
> <snip>
> LC_CTYPE=en_GB.UTF-8
>
> $ 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
>
> $ unset LC_CTYPE
>
> $ foo
> No command 'foo' found, did you mean:
> - Command 'fio' from package 'fio' (universe)
> - Command 'goo' from package 'goo' (universe)
> - Command 'fop' from package 'fop' (main)
> - Command 'fox' from package 'objcryst-fox' (universe)
> - Command 'xoo' from package 'xoo' (universe)
> - Command 'fgo' from package 'fgo' (universe)
> - Command 'zoo' from package 'zoo' (universe)
> + Command 'fio' from package 'fio' (universe)
> + Command 'goo' from package 'goo' (universe)
> + Command 'fop' from package 'fop' (main)
> + Command 'fox' from package 'objcryst-fox' (universe)
> + Command 'xoo' from package 'xoo' (universe)
> + Command 'fgo' from package 'fgo' (universe)
> + Command 'zoo' from package 'zoo' (universe)
> foo: command not found
>
> Steps to reproduce:
>
> Run "LC_CTYPE=foo f"
>
> ** Description changed:
>
> - command-not-found crashes when the LC_TYPE is defined in the environment
> - but is not installed. This can be seen via SSH which sets the LC_TYPE.
> + command-not-found crashes when the LC_CTYPE is defined in the
> + environment but is not installed. This can be seen via SSH which sets
> + the LC_CTYPE.
>
> $ env
> TERM=xterm
> SHELL=/bin/bash
> <snip>
> LANG=en_US.UTF-8
> <snip>
> LC_CTYPE=en_GB.UTF-8
>
> $ 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
>
> $ unset LC_CTYPE
>
> $ foo
> No command 'foo' found, did you mean:
> Command 'fio' from package 'fio' (universe)
> Command 'goo' from package 'goo' (universe)
> Command 'fop' from package 'fop' (main)
> Command 'fox' from package 'objcryst-fox' (universe)
> Command 'xoo' from package 'xoo' (universe)
> Command 'fgo' from package 'fgo' (universe)
> Command 'zoo' from package 'zoo' (universe)
> foo: command not found
>
> Steps to reproduce:
>
> Run "LC_CTYPE=foo f"
>
> --
> You received this bug notification because you are subscribed to
> command-not-found.
> https://bugs.launchpad.net/bugs/1378406
>
> Title:
> Unknown LC_CTYPE causes crash
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/command-not-found/+bug/1378406/+subscriptions
http:// www.zygoon. pl/2013/ 04/why- is-command- not-found- crashing. html
On Tue, Oct 7, 2014 at 5:20 PM, Ben Howard <email address hidden> wrote: en_GB.UTF- 8 /bugs.launchpad .net/command- not-found/ +filebug en_GB.UTF- 8 /bugs.launchpad .net/command- not-found/ +filebug /bugs.launchpad .net/bugs/ 1378406 /bugs.launchpad .net/command- not-found/ +bug/1378406/ +subscriptions
> Marking as confirmed, I can see this happen as well.
>
> ** Changed in: command-not-found
> Status: New => Confirmed
>
> ** Description changed:
>
> - When I SSH on to a pristine cloud instance, I see a crash:
> + command-not-found crashes when the LC_TYPE is defined in the environment
> + but is not installed. This can be seen via SSH which sets the LC_TYPE.
>
> $ env
> TERM=xterm
> SHELL=/bin/bash
> <snip>
> LANG=en_US.UTF-8
> <snip>
> LC_CTYPE=
>
> $ foo
> Sorry, command-not-found has crashed! Please file a bug report at:
> https:/
> Please include the following information with the report:
>
> command-not-found version: 0.2.44
>
> $ unset LC_CTYPE
>
> $ foo
> No command 'foo' found, did you mean:
> - Command 'fio' from package 'fio' (universe)
> - Command 'goo' from package 'goo' (universe)
> - Command 'fop' from package 'fop' (main)
> - Command 'fox' from package 'objcryst-fox' (universe)
> - Command 'xoo' from package 'xoo' (universe)
> - Command 'fgo' from package 'fgo' (universe)
> - Command 'zoo' from package 'zoo' (universe)
> + Command 'fio' from package 'fio' (universe)
> + Command 'goo' from package 'goo' (universe)
> + Command 'fop' from package 'fop' (main)
> + Command 'fox' from package 'objcryst-fox' (universe)
> + Command 'xoo' from package 'xoo' (universe)
> + Command 'fgo' from package 'fgo' (universe)
> + Command 'zoo' from package 'zoo' (universe)
> foo: command not found
>
> Steps to reproduce:
>
> Run "LC_CTYPE=foo f"
>
> ** Description changed:
>
> - command-not-found crashes when the LC_TYPE is defined in the environment
> - but is not installed. This can be seen via SSH which sets the LC_TYPE.
> + command-not-found crashes when the LC_CTYPE is defined in the
> + environment but is not installed. This can be seen via SSH which sets
> + the LC_CTYPE.
>
> $ env
> TERM=xterm
> SHELL=/bin/bash
> <snip>
> LANG=en_US.UTF-8
> <snip>
> LC_CTYPE=
>
> $ foo
> Sorry, command-not-found has crashed! Please file a bug report at:
> https:/
> Please include the following information with the report:
>
> command-not-found version: 0.2.44
>
> $ unset LC_CTYPE
>
> $ foo
> No command 'foo' found, did you mean:
> Command 'fio' from package 'fio' (universe)
> Command 'goo' from package 'goo' (universe)
> Command 'fop' from package 'fop' (main)
> Command 'fox' from package 'objcryst-fox' (universe)
> Command 'xoo' from package 'xoo' (universe)
> Command 'fgo' from package 'fgo' (universe)
> Command 'zoo' from package 'zoo' (universe)
> foo: command not found
>
> Steps to reproduce:
>
> Run "LC_CTYPE=foo f"
>
> --
> You received this bug notification because you are subscribed to
> command-not-found.
> https:/
>
> Title:
> Unknown LC_CTYPE causes crash
>
> To manage notifications about this bug go to:
> https:/