160898 - Mozilla won't start up properly when application folder contains Unicode character

Status: VERIFIED WORKSFORME

(Core :: Internationalization, defect)

Description

[Greg K.]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.0) Gecko/20020801
BuildID:    2002080303

If a Unicode character is added to the name of the folder containing the Mozilla
application, then the Mozilla application will not start up completely.

Reproducible: Always
Steps to Reproduce:
1. Append the text " 1.1" to the name of the Mozilla folder
2. Select the Unicode Hex Input keyboard layout
3. Press option+03b2 to insert the Greek lowercase beta character
4. Press return
5. Launch Mozilla

Actual Results:  Mozilla fails to start up completely. Only the Mozilla menubar
item is shown, and a small window fragment is visible just underneath the
menubar. Mozilla can be quit successfully at this point, though.

Expected Results:  Mozilla should have started up completely.

Though the method is different, the results resemble those of bug 138827.

Comment 1

[Matthias Versen [:Matti]]

-> Int

Comment 2

[Greg K.]

Adding qawanted to match Matti's DUPEME.

Comment 3

[Roy Yokoyama]

ruix: do we have a duplicate bug?  This sounds familiar to MacOS.

Comment 4

[Rui Xu]

It happens when the application path contain unicode characters, it might be 
related to bug 107181.

Comment 5

[Frank Tang]

bad bug. estimate of efforts 7 days

Comment 6

[Frank Tang]

assign 

Comment 7

[Greg K.]

Apparently WorksForMe using FizzillaMach/2003020603. I appended U03B2 to the
Mozilla package name, and it launched successfully.

Comment 8

[Yuying Long]

It's actually crashed when I rename netscape Mach-O 02-19 package name contains
03B2 on Mac 10.2.4.  Not sure if it is blocked by bug 191234.

I'm re-open this bug for now, will follow a crash report. 

Comment 9

[Yuying Long]

Attachment: crash log file with 02-19 Mach-O build on 10.2.4

Comment 10

[Greg K.]

Yuying, you should probably file that as a separate bug. Also, I see possible
AIM-related stuff on that stack ("nsAimSession"); does this belong on Bugscape
rather than Bugzilla? Mozilla doesn't include an AIM client. If your crash
happened on a Netscape build, it belongs on Bugscape instead.

Comment 11

[Yuying Long]

You are right.  Mozilla build doesn't has this problem.  Reslove again as
worksforme.

Comment 12

[Yuying Long]

Verified.