Closed
Bug 185848
Opened 23 years ago
Closed 22 years ago
"Could not initialize the browser's security component" but no details
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: phil, Assigned: ssaux)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.2.1) Gecko/20021215
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.2.1) Gecko/20021215
Reproducible: Always
Steps to Reproduce:
I actually have mozilla SSL working on my original build machine. But when I
take the distrib, and copy it to another machine, it doesnt work with SSL any more.
It's not giving me any debug information beyond the "there may be a disk full,
or permissions problem".
There is no disk full. The shared mozilla binary is owned by root. but running
it as root has the same problem.
$MOZ_HOME/libssl3.so exists and is a valid lib
Actual Results:
Got the pre-canned "Could not initialize.." with no real details of the failure
Expected Results:
GIVE DETAILS on what *exactly * failed!
Not that it should matter any, but I compiled it on a sunblade 100 with gcc
2.95.3. I am running it (and failing SSL) on another sunblade. both running
solaris 8.
Comment 1•22 years ago
|
||
Try (backing up then) removing ~/.mozilla/<..userdir..>/*.db and restarting mozilla.
oops. forgot I had this thing open. sorry.
Thanks for looking at it again
when copying the install, I somehow missed one of the crucial files.
Now that my process copies them, SSL works okay.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•