165063 - [1.1final]installer crash if localize the message in [legacycheck0] (config.ini) to Chinese in case of there is a legacy mozilla installed.

Status: RESOLVED INVALID

(SeaMonkey :: Installer, defect)

Description

[shaohua wen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; zh-CN; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; zh-CN; rv:1.1) Gecko/20020826

if I localize the latest string in config.ini for installer.
and if there is an old mozilla installed into /usr/local/mozilla
,the installer segment fault.

;-------------------------------------------------------------------------
[LegacyCheck0]
;-------------------------------------------------------------------------
Filename=mozilla-bin
; *** LOCALIZE ME BABY ***
Message=¼ì²âµ½Ò»¸ö¾ÉµÄMozilla°²×°¡£Çë°´¡°É¾³ý¡±°´Å¥Ñ¡Ôñɾ³ýµ±Ç°ÒÑ°²×°Mozilla°æ±¾µÄ
Îļþ¼ÐÖеÄÄÚÈÝ»òÕß°´¡°È¡Ïû¡±°´Å¥À´Ñ¡Ôñ½«Mozilla°²×°µ½Ò»¸öеÄÎļþ¼Ð¡£

----------------------------------
works fine if changed the Message back to english.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[K'Trina Medina]

CCing andreasb. To be reassigned to Intl.

Andreas, 
Can you tell Shaohua how to go about localizing the config.ini file to Chinese?  

Comment 2

[Andreas Becker]

CCing Bob Jung for international.

Comment 3

[K'Trina Medina]

Can someone in Intl please confirm this bug or change the status of this bug,
and reassign it to an Intl QA Contact? I need to get it off my radar.
Thanks-a-bunch!

Comment 4

[Andreas Becker]

Bob, can you please re-assign the QA contact to someone in the intl. team? Thanks.

Comment 5

[bobj]

reassigned to Marina for now...

Ying,  Can you help verify this bug?

Comment 6

[Ying-Lin Xia]

? Looks like [LegacyCheck0] is only for unix/mac, see:
    http://lxr.mozilla.org/seamonkey/search?string=LegacyCheck0
I checked win32 installer, 1.1final and the trunk, no any win32 config.ini does
contain this string.

Reporter, more detail infomation please.

Comment 7

[Shaohua Wen]

Sorry ,I reported from my win32 build of mozilla before,this bug is in Linux
platform.
the last string in the config.ini file.

Comment 8

[Ying-Lin Xia]

Thanks, Shaohua. More questions:
1) The summary says "1.1final" but the "Version" section shows "Trunk", which
one you are working at?
2) Which Linux you are using? RedHat? Which version, 7.x? 8.0? What locale
setting you have?

Comment 9

[Shaohua Wen]

I've tried from 1.0 to 1.1a,1.1b,1.1 final,and  1.2a ,1.2b (later),the installer
have the same problem.I reported this issue a long time ago,and at that time,the
latest version of mozilla is 1.1 final.
the platform I tried is Mandrake 8.1 and Root Linux 1.3(kernel 2.4.18),Redhat
not tested.
the locale settings is zh_CN.GB2312
I will upload the config.ini that will crash the installer,and the working one.

Comment 10

[Shaohua Wen]

Attachment: the working one

the working one config.ini

Comment 11

[Shaohua Wen]

Attachment: The one crashes the installer

the config file that will crash the installer

Comment 12

[Ying-Lin Xia]

Thanks for the info, Shaohua. And I can reproduce the crash on RedHat Linux 8.0.

1) I think this is because some ugly parser code in:
http://lxr.mozilla.org/seamonkey/source/xpinstall/wizard/unix/src2/nsSetupTypeDlg.cpp#889
It is an intl bug in the installer.

2) Marina, can you please assign this bug to me, so I can have a try?

3) Shaohua, the current workaround is: make your string shorter and with some
extra ASCII spaces between the string. Here is a working example:
Message= ¼ì²âµ½Ò»¸ö¾ÉµÄ Mozilla ¡£Çë°´¡°É¾³ý¡±°´Å¥É¾³ýµ±Ç°ÒÑ°²×°µÄ Mozilla »ò°´¡°È¡
Ïû¡±°´Å¥Ñ¡ÔñÒ»¸öеÄÎļþ¼Ð¡£ 
(Note there are spaces at the beginning of the string, and also the end of the
string.)

Comment 13

[marina]

reassigning to Ying

Comment 14

[Alexander Opitz]

What is the state of this bug?

Comment 15

[Max Kanat-Alexander]

No reply in two months. Closing bug.

-M

Comment 16

[Shaohua Wen]

Dear Max K-A,
    There is just a workaround now,Why close this bug as invalid?
In Comment#12 Ying-Lin Xia  can reproduce this bug,
So I think that this bug should be changed to as assigned.
Bye, Holy

Comment 17

[Max Kanat-Alexander]

If yxia can still reproduce the bug, and still wants to fix it, then the bug can
be re-opened. I didn't mean to be rude -- INVALID is the only way to close a bug
that is apparently not a going concern anymore.

You'll notice that comment 12 was nine months ago, and then there wasn't a
follow-up, when one was asked for, in two months. If somebody else wants to take
the bug and they can still reproduce it, point them this way and ask them to
re-open it!

-M