86198 - Moving then launching Mozilla produces Application Launch failure dialog

Status: VERIFIED WONTFIX

(SeaMonkey :: Build Config, defect, P3)

Description

[Chris Petersen]

Build: 2001061314
Platform: Mac OS X
Expected Results: Application is outside of default directory and error message
appears.
What I got: It's understand to me why I got this error, but should we at least
add this to a Read me file ?

Steps to reproduce:

1) Move the Mozilla application out of the default directory (I moved it to the
desktop)
2) Launch app from the new location
3) Error message appears: 
Application Launch Failure
The application 'Mozilla' cound not be launched because of a shared library
error: "A"
4) Not very descriptive to the average user so we might explain why this maybe
happening in the Read me.

Comment 1

[Asa Dotzler [:asa]]

over to some folks that might be able to help

Comment 2

[Mike Pinkerton (not reading bugmail)]

i'd assume 4.x has this same problem and we're not likely to waste time fixing
it. if the only fix is documentation, then i shouldn't own it.

Comment 3

[Simon Fraser [no longer active]]

4.x did put up a dialog saying that "Essential Files" was missing. We can't get 
that far, because we fail to load needed libraries up-front.

I think the real answer to this (esp. on X) is to use a package.

Comment 4

[Adam Masri]

I believe packages are bug 83705. This might be fixed by fixing that bug, but
maybe not. Therefore, setting a dependency. We can see if this is fixed when
that one is done.

- Adam

Comment 5

[Asa Dotzler [:asa]]

I think this belongs in Build Config. 

Comment 6

[Jon Granrose]

mac == jj

anyone think this needs to be nsbranch, or can we just relnote it?

Comment 7

[J.J. Enser]

This will effectively be taken care of by creating an Application Bundle on OSX.
(bug 83705, as indicated above).
Fixing this for MacOS 8/9 would require bootstrap code change.

Comment 8

[Steve Dagley]

As jj noted, we're gonna make this harder to do for the Mac OS X version. 
Marking WONTFIX since we're not going to be trying to prevent it for the classic
app.

Comment 9

[Jon Granrose]

verified wontfix.