Closed Bug 165073 Opened 22 years ago Closed 22 years ago

Browser will not start on Mac OS X 10.2

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 86538

People

(Reporter: albert, Assigned: asa)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mac OSX 10.2 Mozilla 1.1 Gecko 20020826

Brand new install of OS X 10.2 (not an upgrade). Most recent release version of
Mozilla dies immediately after the splash screen. 

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Go to ~/Library/Mozilla/Profiles/Default/<profile_name>/ and move your bookmarks
and prefs.js to some place. Then throw away the Mozilla folder and launch
Mozilla. Put the bookmarks and prefs.js back into the new profile folder.

Actually, you might first want to conclude that there really is a <profile_name>
(consisting of random characters) in the Mozilla/Default folder, since Mozilla
will in fact not start without it (assuming there has been one before).
It's not necessary to be dragging profile folders around manually. Just try
creating a new profile using the Mozilla Profile Manager.

albert@groupm7.com, when you say it "dies," what you you mean? Does it
unexpectedly quit? Does it hang? Does it hang the OS?

See also bug 164749.
Summary: Browser will not start → Browser will not start on Mac OS X 10.2
Profile Manager? Doesn't work. Never did work. At least it isn't very obvious
how to use it. The help files (specific to Netscape) don't help either.

Thus, manual tinkering is necessary.

By dies, I mean it flashes a splash screen and goes away. No other activity - no
error, no hanging, nothing.
Re: comment 3, the Profile Manager works by launching it instead of Mozilla. (Or
drag it to the Mozilla app icon if you have multiple Mozillas installed to be
sure you launch the right one.) You're saying that never worked? It's always
worked for me.
Would the fact that the disk is formatted UFS (as opposed to HFS) have anything
to do with this?

Is there an error log produced anywhere?
Albert, yes. In that case, this is a dup of bug 86538.
The bug 86538 discussion doesn't seem to think this is a high-priority issue. Am
I reading that right?!?!
Albert, you should ask there. 

*** This bug has been marked as a duplicate of 86538 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.