125415 - Mac Mozilla should do better sanity checking at startup, and nicely tell the user when it can't run

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Simon Fraser [no longer active]]

We have a number of bugs that cause Mozilla to fail to start up on Mac, and also 
need to do more careful Gestalt checking to make sure that we can run at all. For 
example, we bail if run off a locked volume (bug 104954). We'll die less or more 
horribly of the .xpt files are missing, or if the user deleted the Components 
directory. We should put up a nice (native) dialog in these causes to tell the 
user what's wrong.

Comment 1

[Peter Trudelle]

->jag

Comment 2

[jag (Peter Annema)]

Isn't this an XP issue?

Comment 3

[jag (Peter Annema)]

-> future

Comment 4

[sairuh (rarely reading bugmail)]

->k'trina, who [iirc] tests many startup features...

Comment 5

[K'Trina Medina]

Grace, do you know?

Re: Comment #4
->k'trina, who [iirc] tests many startup features...

Comment 6

[Grace Bush]

Don't think that is Installer- maybe browser- I guess we would find this when we 
get to sanity checks but not sure if it falls in Install issues

adding Dan

Comment 7

[Simon Fraser [no longer active]]

Mac OS X builds don't have an installer, so this is not an insaller issue.

Comment 8

[Simon Paquet [:sipaq]]

This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".

Comment 9

[Martin Creutziger [:MMx]]

Mozilla (Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-AT; rv:1.8a1)
Gecko/20040520) runs fine from a locked Volume in MacOS X 10.3.3. So I think
this is a different situation now.
I think this is fixed or has been fixed by the different OS architecture.

Comment 10

[Martin Creutziger [:MMx]]

revoking comment #9. Moz1.8a1 crashes without error message if ~/Library is
write-protected.

So there still *is* a problem with that on OS X.

Comment 11

[riscky]

per comment #10
changing form 9.x to 10.x

Comment 12

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 13

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420