46534 - Crash at launch after selecting installed locale

Status: VERIFIED FIXED

(Core :: Internationalization, defect, P3)

Description

[Jimmy Lee]

Build: 2000-07-26-09-M17(WIN), 2000-07-26-08-M17(MAC), 2000-07-26-08-M17(LINUX)

1. Delete Default profile
2. Install Seamonkey (commerical or mozilla)
3. Open http://jimbob/jars/a_ichrome_locale.html
4. Click Install button from html page
5. Click OK button from dialog that appears to install locale
6. From View menu, choose Set Language/Region, and choose ichrome_locale
7. Exit Seamonkey
8. Launch Seamonkey

RESULT:
Dialog appears with text:
XML Parsing Error: undefined entity
Line Number 141, Column 29:
accesskey = "&reloadCmd.accesskey;"
-------------------------------^

There are no menu names on the menu bar.  Seamonkey appears to be running.  A 
force quit gets the user out.  Relaunching repeats the same problem.  Removing 
the Default directory restores the ability to launch gracefully.

EXPECTED RESULT:
No error dialog.  Launches happily ever after.

NOTE:
Stumbled across this anomaly investigating Bug 39367.  I'm not even sure if the 
locale package that is installed from step# 4 above is legitimate.  Is this an 
isolated case or general problem?  I'm not sure if I have the correct Component, 
but I'm confident we can get this routed to the right people from here.  Thanks.

Comment 1

[Jimmy Lee]

Adding keyword crash.

Comment 2

[nhottanscp]

Tao, could you look at this?

Comment 3

[Jimmy Lee]

Attachment: Screen shot of dialog XML Parsing Error

Comment 4

[tao]

It appeared that you are using the ja-JP pack which might not be up-to-date yet.

Hi, Michele:


Until we bring the ja-JP pack up-to-date, we won't be able to use it in daily 
build. I am reassigning this bug to you until such pack is furnished.

Thanks

Comment 5

[Jimmy Lee]

I got the ja-JP pack from Bug 39367.  It's true that I don't know if the pack is 
complete.  I'm not sure what it is suppose to do.  We certainly should check 
with a known completed pack.

Also, this raises the issue of the behavior if the pack is not complete.  The 
behavior in this case is not good.  Is there some way to validate the pack 
before trying to use it?  I'm not close to this area, but it would be preferred 
to have some kind of "auditing" before accepting the pack.

Comment 6

[Michele Carlson]

reassign to Ray

Comment 7

[tao]

This problem should have been fixed!

Comment 8

[tao]

This seems to be a US build.

Comment 9

[tao]

this is fixed now since the ja-JP pack is in sync with the US (m17) build.

Comment 10

[Teruko Kobayashi]

Changed QA contact to [e-mail].
Rob, please verify this.

Comment 11

[Rob Spain]

changing QA contact

Comment 12

[Teruko Kobayashi]

Verified.