Bug #43901 MEM installer fails to execute on the directory contains japanese character.

Description:
MEM installer fails to execute on the directory contains japanese.

For example, Ubuntu 8.1 japanese edition use デスクトップ instead of Desktop, so if user download *.bin installer of MEM on that directory, it fails like this,

meijik@meijik-laptop:~/デスクトップ$ ./mysqlmonitor-2.0.5.7153-linux-x86-install
er2.bin 
Installer payload initialization failed. This is likely due to an incomplete or corrupt downloaded file.

To avoid this problem, move *.bin to a directory don't contains japanese and run it.

How to repeat:
See description.

Suggested fix:
[Workaround]

Run *.bin file on the directory not contains japanese(or may be happend on another non alphabetic characters).

[Suggested Fix]

Modify installer or need to document this as note.

We are looking into this but it may require core changes to how the installer runtime is initialized and it will take us some time to implement.

Patch sent to Keith.

Keith Russell writes: 
Patch installed in versions => 2.1.0.1076.

I can install MEM server 2.1.0.1096 on Linux with Japanese directory, but it appears the installer fails to initialize bundled MySQL Server. The log follows:

 インストール中
 0% ______________ 50% ______________ 100%
 ########################################警告: Problem running post-install step. Installation may not complete correctly
 実行中にエラーが起きました 
/home/mikiya/日本語/enterprise/monitor/mysql/scripts/mysql_install_db 
--defaults-file=/home/mikiya/日本語/enterprise/monitor/mysql/my.cnf --user=mysql : 
child process exited abnormally
続けるには [Enter] キーを押してください ：

Carsten Segieth writes: 
Re-opening per the last comment. 
- can you install a MySQL server into the same path as it is choosen with the MEM install?
- if this works please create a debug log from the installer (add --debugtrace <debugtrace_file> on the command line, perhaps also --debuglevel 5 for the highest debug level)
- please attach the debugtrace file and any other logs that could help tracking down the problem, e.g. the newest bitrock* files from the /tmp dir.

Carsten Segieth writes: 
... and any logs from the mysql dir