Closed
Bug 191533
Opened 22 years ago
Closed 22 years ago
Mac OS X Mozilla (Mach-O) fails to launch
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: pbergsagel, Assigned: asa)
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1b) Gecko/20020723
Build Identifier: MachO nightly from 01/31/03 for Mac OS X
I downloaded the MacOSX (MachO) nightly from January 31, 2003. Upon clicking the
application Icon the icon bounces a few times in the dock appearing to launch.
The application quits before any application window appears.
Reproducible: Always
Steps to Reproduce:
1.Launch Mozilla
2.Application fails to launch and quits.
Actual Results:
Mozilla quits before it has launched.
Expected Results:
I expectwed the Mozilla to finish launching.
I tried the build from 01/31 and 01/30. I could not find an earlier build to
test. My last working build was either from the 27th or 28th, but I had deleted
this build before I realized this nightly would not launch.
Reporter | ||
Updated•22 years ago
|
Keywords: crash,
mozilla1.3
Comment 1•22 years ago
|
||
I am typing this from the MachO nightly that i downloaded earlier this afternoon:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030201
Are you still having problems with this build?
WorksForMe using FizzillaMach/2003013103. Paul, did you try another profile?
URL: N.A.
Summary: MacOS X Mozilla (MachO) fails to launch. → Mac OS X Mozilla (Mach-O) fails to launch
Comment 3•22 years ago
|
||
I'm using build 2003013103 on Mac OS X 10.2.3 - this build works for me.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030131
Reporter | ||
Comment 4•22 years ago
|
||
There is a comment on MozillaZine by BjarneDM posted on Sat Feb 01, 2003 12:10
pm and titled -> !!!WARNING!!! broken build !!!. It is ithe 10th post in the
particular thread. He confirms the problem which I am experiencing. The url link
to the Mozillazine thread is below:
http://www.mozillazine.org/forums/viewtopic.php?t=5073
This Mozillazine post confirms the bug I am experiencing. I suspect that the
nightly build from January 31st lost track of the location of my profile. If I
could have remembered how to launch Macho's profile Manager from the command
line I believe I could have solved the issue by directing Mozilla to the
location of the profile. This is why we need easy access to the profile manager
in the MachO build.
I did not try a new profile. The reason is I don't remember how to access the
profile manager from the command line. (This is a seperate issue, but there is
a need for the MachO build to include an easier method to launch the profile
manager then with the command line.)
Reporter | ||
Comment 5•22 years ago
|
||
I forgot to mention that I located a copy of the MachO build from January 27.
After a few failed lauches it located my profile and launched. The build from
January 31 would not recognize my profile n matter how many times I launched it.
Comment 6•22 years ago
|
||
> If I could have remembered how to launch Macho's profile Manager from the
command line
% cd Mozilla.app/Contents/MacOS
% ./mozilla-bin -ProfileManager
Comment 7•22 years ago
|
||
Though, bringing up the profile mgr should not be the way to work around an app
that is crashing at startup. We need to get to figure out why it is crashing and
fix that. Can you attach a crash log?
Reporter | ||
Comment 8•22 years ago
|
||
I am resolving this bug as wfm since I had no problems installing the latest
nightly. It launched as expected. I still feel the original issue was with the
lack of an easy method of accessing the profile manager. About two moths ago I
switched to the Macho from the CFM build. At that point the CFM build's user
profile was imcompatible with the Macho build. At that time launching the Macho
build caused the icon to bounce a few times before the appication quit.
Launching the Macho Build from the command line (to access the profile manager
solved the issue. I could "show" the application where the profile was located.
These symproms seem very similar to what I experience with this bug and I am
sure the issue could have been resolved if I could remember how to launch the
profile manager from a command line or there was an easier method to launch the
profile manager.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•