Karmic: Wubi could not launch with Japanese-multibytes user names

log file

On inquiry, the "unicode" function should take 'mbcs' for 2nd argument if 1st arg includes Japanese character, or aborts.
Additionaly, 1st arg of the "os.path.join" function should be converted to unicode, or it aborts if Japanese characters are given.

I'm attaching a diff file for the wubi source tree(rev158).
I'v compiled wubi with this patch and works fine on my Windows Vista Japanese Edition.
There are probably no ill effects if you use non-Japanese Windows.
I'll be pleased if wubi developers view this patch and comment.

Just a side note: the login name, as well as password fields should never allow anything else than ASCII characters. Everything else would highly depend on the local keyboard layout at login time and could leave the user stranded without the possibility to log into the system. Especially East-Asian IMEs are not supported at login time.

Arne, Thank you for your note. Wubi will copy the login name from the one of Windows, but in the case of using a non-ASCII user name on Windows, it won't copy the name and leave the input feild blank. And we must input other login name for Ubuntu with ASCII characters or Wubi warns. So I think there's no problem at least about login names if using the above patch.

Jun, thanks for the patch, we will try to have it in for karmic, if it is not possible, I will make the patched version of wubi available on wubi-installer.org and ubuntu.com

Applied patch and tested with English username and could not see any regression. Needs further testing.

I've uploaded a fixed version to <http://people.canonical.com/~evand/wubi/karmic/wubi-r159.exe>. If we can get a few more tests using this version, I'll be happy to make sure it gets on the CD. Please reply in this bug report with the version of Windows you used, your internationalization settings, and whether or not the install was successful.

Thanks!

It's worth noting that my wubi r159 build bumped us to grub version 1.97~beta4-1ubuntu3.

Evan:
 I tested with wubi r159 build within below 4 envs, it works for me.
 - Windows Vista Enterprise(SP2) / x64, Japanese
 - Windows Vista Ultimate(SP2) / x64, Japanese
 - Windows Vista Home Premium(SP2) / x86, Japanse
 - Windows XP Professional(SP3) / x86, Japanese

I also tested with wubi r159 on 4 envs below.
It works fine on all.

- Windows 7 Starter / x86, Japanese
- Windows 7 Home Premium / x86, Japanese
- Windows 7 Professional / x86, Japanese
- Windows 7 Professional / x64, Japanese

Okay, stable symlink changed. This will be on the next daily-live CD build.

I tried wubi-r159.exe and wubi-r160.exe ( http://people.canonical.com/~evand/wubi/karmic/ ).
But Wubi still exits immediately.

Windows Vista SP2
Username = "テストアカウント2号"

There is no log file on C:\Users\USERNAME\AppData\Local\Temp.

Sorry I forgot to tell Vista's edition.
Windows Vista Home Premium SP2.

Nobuto this might be due to a different bug. Try the official wubi release, there should be some wubi file in your user temp folder. You can also try to run wubi.exe from command line.

I created new username for Windows Vista and tried another Wubi on http://wubi-installer.org/.
But also exits immediately.

In C:\Users\テストアカウント\AppData\Local\Temp directory,
there are "pyl*.tmp", "Low" and "WPDNSE" folders, which are empty.
"jusched.log", "wmsetup.log", "テストアカウント.bmp" also left.

And also tried from command line(cmd.exe)

C:\Users\テストアカウント>wubi.exe
appears UAC window and allow it.
Then resturn no message and show below line again.
C:\Users\テストアカウント>

After patch which Jun committed,
Kanji and Hiragana (types of Japanese multibyte character) became OK,
but Katakana (a type of Japanese multibyte character) is still have trouble.
http://en.wikipedia.org/wiki/Katakana

"テストアカウント" is consist of Katakana characters.

> this might be due to a different bug.
Agostino, maybe yes.

I will report as a new bug and write a bug number on this thread later.

I reported as Bug #472591.