377529 - Crash early in startup: XML Parsing Error: undefined entity

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, defect)

Description

[Eddie Maddox]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.4pre) Gecko/20070414 SeaMonkey/1.1.1
Build Identifier: seamonkey-1.5a.en-US.mac.dmg  14-Apr-2007 06:19   22M

Mac Blue G3, OSX 10.3.9.all-updates.

With "Mozilla" profile directory deleted,
Since:
seamonkey-1.5a.en-US.mac.dmg  28-Mar-2007 06:20   22M
Crash early in startup:
"
XML Parsing Error: undefined entity
Location: chrome://navigator/content/navigator.xul
Line Number 61, Column 1:<window id="main-window"
^
"
No menus available yet.
To Quit, must use Dock SM icon menu.

Thanks,
Eddie

Reproducible: Always

Comment 1

[Stefan [:stefanh]]

This works for me with a recent trunk build (10.3.9 ppc).

> With "Mozilla" profile directory deleted,

Where was this directory?  If you deleted the yourUserName/Library/Mozilla directory all your profile(s) will be gone.

Comment 2

[Eddie Maddox]

(In reply to comment #1)
> > With "Mozilla" profile directory deleted,
> 
> Where was this directory?  If you deleted the yourUserName/Library/Mozilla
> directory all your profile(s) will be gone.

Which, for testing, is a good idea. Right?

I simply created a testing account on my Mac,
and switch to that when testing each 1.5.A.x nightly.
The bug is still there with the 15 APR build.

I do run 1.1.x nightlies in my "production" environment.
When 1.5.B.xs appear, I'll start using those.

Thanks,
Eddie

Comment 3

[Stefan [:stefanh]]

(In reply to comment #2)
> (In reply to comment #1)
> > > With "Mozilla" profile directory deleted,
> > 
> > Where was this directory?  If you deleted the yourUserName/Library/Mozilla
> > directory all your profile(s) will be gone.
> 
> Which, for testing, is a good idea. Right?

Of course :-)

Do you get a Mozilla directory in your test account library/ when you've started SeaMonkey?

Comment 4

[Eddie Maddox]

(In reply to comment #3)
> Do you get a Mozilla directory in your test account library/ when you've
> started SeaMonkey?

Yes, and that Error message, but no menus or window.
Same results for today's build:
seamonkey-1.5a.en-US.mac.dmg  16-Apr-2007 06:20   22M

Eddie

Comment 5

[Samuel Sieb]

I had the exact same problem on Linux and it was suggested to me to try running as root.  After that, it worked as a regular user.  So it seems there's a problem with running SeaMonkey the first time without write access.

Comment 6

[Robert Kaiser]

Sounds like it's a problem if you have no write permissions to the app directory.

As long as it doesn't happen with suiterunner as well, it's probably not worth trying to find the bug in xpfe though. Try to copy the app to some place where you have write permissions.

If it really turns out to be xpfe-only, we should WONTFIX it, as we're planning to switch to suiterunner as soon as reasonably possible.

Comment 7

[Andrew Schultz]

Actually, I suspect bug 376173 based on comment 5, which happens as a result of a branch that already has approval to land on the branch.  So that would make this extremely important.

Comment 8

[Wayne Mery (:wsmwk)]

If andrew is right, this should be gone.
can you reproduce?

Comment 9

[Philip Chee]

XPFE is Dead and long gone. So this is either WORKSFORME or WONTFIX. Either way closing.