Closed
Bug 59566
Opened 24 years ago
Closed 24 years ago
PSM Crashing under certain funky circumstances.
Categories
(Core Graveyard :: Security: UI, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: bugzillaabuse, Assigned: javi)
Details
(Keywords: crash, relnote, Whiteboard: relnote-user)
Happens in: NT 11-08-09
Does not happen in: Mac 11-07-17, Linux 11-05-09
Reason for Severity: Crashing.
Reproducible: Always, when it happens once.
Steps to Reproduce:
1. Open browser
2. Use any PSM related feature (visiting http://www.accountonline.com will do)
Actual Results: PSM.EXE failure.
Expected Results: Would be nice if it worked.
Assignee | ||
Comment 1•24 years ago
|
||
This is caused by a corrupt component.reg file.
If you delete the file at
c:\program files\common file\netscape shared\security\component.reg
the crash should go away. (At least it did for me.)
Assignee | ||
Comment 2•24 years ago
|
||
Is there any way we can get this release noted?
Assignee | ||
Comment 3•24 years ago
|
||
Can we add release note that says something along the following lines:
If PSM crashes for you everytime you try to make an SSL connection, this is most
likely caused by a corrupt component.reg file. To fix this, remove the file
C:\Program Files\Common Files\Netscape Shared\Security\component.reg and then
re-launch Netscape6. At this point you should be able to do SSL connections again.
Keywords: relnote
Adding Status Whiteboard as well. By the way, this solution worked for me.
Whiteboard: relnote-user
changing QA contact to junruh@netscape.com
QA Contact: nitinp → junruh
Comment 6•24 years ago
|
||
Marking worksforme.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 8•24 years ago
|
||
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Comment 9•24 years ago
|
||
Mass changing Security:Crypto to PSM
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•