autojump

Bug #916538 reported by SolomonPhiloSophia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
command-not-found
Incomplete
Undecided
Unassigned

Bug Description

solo@solo-Satellite-L650:~$ j aut
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
solo@solo-Satellite-L650:~$ j ini
/media/now/Dropbox/system_variable/sys_init
solo@solo-Satellite-L650:/media/now/Dropbox/system_variable/sys_init$ j aut
/home/solo/.config/autostart
solo@solo-Satellite-L650:~/.config/autostart$

ubuntu 11.10, 64b

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

Hello

Were you using a remote connection (putty/ssh) from another machine?

Changed in command-not-found:
status: New → Incomplete
Revision history for this message
SolomonPhiloSophia (solomonphilosophia) wrote : Re: [Bug 916538] Re: autojump

  it is guake terminal, my own laptop.

i just copied the display which means only the first command lead to the
crash. the following two worked well. ( i did nothing between these
commands )

On 2012年01月17日 21:51, Zygmunt Krynicki wrote:
> Hello
>
> Were you using a remote connection (putty/ssh) from another machine?
>
> ** Changed in: command-not-found
> Status: New => Incomplete
>

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

What is your terminal's character encoding?

This crash happens when the terminal is sending something that does not match system's expectation. You can use any encoding you like as long as both the terminal and system locale settings agree on this.

You can examine locale settings by running:

$ locale

And you need to check your terminal (I'm not familiar with it) to see how to set it up.

Revision history for this message
SolomonPhiloSophia (solomonphilosophia) wrote :

a drop-down/pop-up terminal emulator similar with tilda. and i just met
this issue for once.

my locale is cn, and i run the terminal emulator in my ubuntu, so i
think the locales are the same.
LANG=zh_CN.UTF-8
LANGUAGE=zh_CN:en
LC_CTYPE=zh_CN.UTF-8
LC_NUMERIC="zh_CN.UTF-8"
LC_TIME="zh_CN.UTF-8"
LC_COLLATE=zh_CN.UTF-8
LC_MONETARY="zh_CN.UTF-8"
LC_MESSAGES=zh_CN.UTF-8
LC_PAPER="zh_CN.UTF-8"
LC_NAME="zh_CN.UTF-8"
LC_ADDRESS="zh_CN.UTF-8"
LC_TELEPHONE="zh_CN.UTF-8"
LC_MEASUREMENT="zh_CN.UTF-8"
LC_IDENTIFICATION="zh_CN.UTF-8"
LC_ALL=

as this is not a problem for me, i just report this bug for your
convenience and hope helpful for you.
if it is not a problem ( for example, i just met once) for the others,
then we could close this issue.
however, if i could give any help, please do not hesitate to tell me.
:)

On 2012年01月18日 15:44, Zygmunt Krynicki wrote:
> What is your terminal's character encoding?
>
> This crash happens when the terminal is sending something that does not
> match system's expectation. You can use any encoding you like as long as
> both the terminal and system locale settings agree on this.
>
> You can examine locale settings by running:
>
> $ locale
>
> And you need to check your terminal (I'm not familiar with it) to see
> how to set it up.
>

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

Other bug subscribers

Remote bug watches

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