Closed
Bug 1197746
Opened 9 years ago
Closed 7 years ago
Login manager fails to initialize with this cert8.db
Categories
(NSS :: Libraries, defect)
NSS
Libraries
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ke5trel, Unassigned)
Details
Attachments
(1 file)
615 bytes,
application/zip
|
Details |
The attached cert8.db produces the following error:
> NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIPK11Token.initPassword] crypto-SDR.js:66:0
> Error: Initialization failed storage-json.js:96:13
> NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: [JavaScript Error: "Initialization failed" {file: "resource://gre/components/storage-json.js" line: 96}]'[JavaScript Error: "Initialization failed" {file: "resource://gre/components/storage-json.js" line: 96}]' when calling method: [nsILoginManagerStorage::initialize] nsLoginManager.js:125:0
> [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: resource://gre/modules/XPCOMUtils.jsm :: XPCU_serviceLambda :: line 228" data: no]
It came from a profile I used for some time (1-2 years) exclusively on release versions, I never stored passwords or touched certificates and the profile seems to be otherwise healthy.
Opening "Security Devices" shows the standard two entries plus multiple duplicates with empty contents.
Attempting to open the file with certutil fails.
> "certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key database is in an old, unsupported format."
Looking inside the file with a hex editor it looks almost completely empty.
Failure to initialize the login manager causes context menus to fail in 42.0a2 (Bug 1197559).
Assignee: nobody → nobody
Component: Password Manager → Libraries
Product: Toolkit → NSS
Version: Trunk → trunk
Comment 1•7 years ago
|
||
Please reopen if this is still valid.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•