Closed
Bug 150762
Opened 24 years ago
Closed 24 years ago
New mozilla doesn't get past mozilla profile manager
Categories
(Core Graveyard :: Profile: BackEnd, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: timball, Assigned: ccarlen)
Details
Using red-carpet on a RH 7.2 machine I upgraded to mozilla 1.0 from 0.9.9. Upon
start of mozilla the Mozilla Profile Manager brings up it's dialog box prompting
me to create a new profile.
Clicking anything that you would assume would make the profile manager quit and
mozilla start causes the following error to be printed in a pop-up window:
"Component returned failure code: 0x80004005 (NS_ERROR_FAILURE)
[nslProfileInternal.startApprunner]"
The "fix" that I had to do was: mv ~/.mozilla ~/mozilla then copy back my
bookmarks and reset all the preferences.
frank informs me this is not his bug and he'll close this on ximian's
bugzilla.... <sigh> guess I have to cut and paste this to send to mozilla's
actual bugzilla.
Comment 1•24 years ago
|
||
proken profiles could happen before 1.0..
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 2•24 years ago
|
||
Verified WFM.
Tim, please reopen if this problem still exists on 1.0+ builds.
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•