missing logins and passwords after upgrade to 48

RESOLVED INVALID

Status

()

Firefox
Untriaged
RESOLVED INVALID
a year ago
a year ago

People

(Reporter: Igor, Unassigned)

Tracking

48 Branch
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

a year ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0
Build ID: 20160805135620

Steps to reproduce:

upgraded to firefox 48


Actual results:

All saved logins and passwords disappeared.  When I start firefox in safe mode --- all login and passwords in place. When i start forefox with all addons disabled --- password and logins still missing. I do use master password---it is working as expected in safe mode. 


Expected results:

Saved passwords and logins shouldn't disapear
(Reporter)

Updated

a year ago
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Summary: missing passwords after upgrade to 48 → missing logins and passwords after upgrade to 48
(Reporter)

Comment 1

a year ago
When I start firefox in a command I see some errors that maybe relevant:

$ firefox 
console.error: 
  Error sanitizing siteSettings
  Message: [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 230"  data: no]
  Stack:
    XPCU_serviceLambda@resource://gre/modules/XPCOMUtils.jsm:230:14
XPCU_defineLazyGetter/<.get@resource://gre/modules/XPCOMUtils.jsm:198:21
Sanitizer.prototype.items.siteSettings.clear<@chrome://browser/content/sanitize.js:559:15
TaskImpl_run@resource://gre/modules/Task.jsm:319:40
TaskImpl@resource://gre/modules/Task.jsm:280:3
createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:254:14
Sanitizer.prototype._sanitize<@chrome://browser/content/sanitize.js:167:33
TaskImpl_run@resource://gre/modules/Task.jsm:319:40
TaskImpl@resource://gre/modules/Task.jsm:280:3
createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:254:14
Sanitizer.prototype.sanitize<@chrome://browser/content/sanitize.js:68:19
TaskImpl_run@resource://gre/modules/Task.jsm:319:40
TaskImpl@resource://gre/modules/Task.jsm:280:3
createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:254:14
sanitizeOnShutdown<@chrome://browser/content/sanitize.js:877:9
TaskImpl_run@resource://gre/modules/Task.jsm:319:40
TaskImpl@resource://gre/modules/Task.jsm:280:3
createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:254:14
Sanitizer.onStartup<@chrome://browser/content/sanitize.js:866:11
TaskImpl_run@resource://gre/modules/Task.jsm:319:40
TaskImpl@resource://gre/modules/Task.jsm:280:3
createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:254:14
BG__finalUIStartup@resource://app/components/nsBrowserGlue.js:723:5
BG_observe@resource://app/components/nsBrowserGlue.js:268:9

Vector smash protection is enabled.
WARNING: A blocker encountered an error while we were waiting.
          Blocker:  sanitize.js: Sanitize
          Phase: Places Clients shutdown
          State: {"progress":{"cache":"cleared","cookies":"cleared","offlineApps":"blocking","history":"cleared","formdata":"blocking","downloads":"cleared","sessions":"blocking","siteSettings":"blocking"}}
WARNING: Error: Error sanitizing
WARNING: Sanitizer.prototype._sanitize<@chrome://browser/content/sanitize.js:187:13
TaskImpl_run@resource://gre/modules/Task.jsm:319:40
Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:937:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:750:11
(Reporter)

Comment 2

a year ago
And after the output in comment above repeatedly:

*************************
A coding exception was thrown and uncaught in a Task.

Full message: TypeError: Services.logins is undefined
Full stack: LoginManagerParent.updateLoginAnchor<@resource://gre/modules/LoginManagerParent.jsm:497:5
TaskImpl_run@resource://gre/modules/Task.jsm:319:40
TaskImpl@resource://gre/modules/Task.jsm:280:3
createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:254:14
updateLoginFormPresence/state.anchorDeferredTask<@resource://gre/modules/LoginManagerParent.jsm:485:15
createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:243:18
Task_spawn@resource://gre/modules/Task.jsm:168:12
this.DeferredTask.prototype._timerCallback/<@resource://gre/modules/DeferredTask.jsm:282:13
TaskImpl_run@resource://gre/modules/Task.jsm:319:40
TaskImpl@resource://gre/modules/Task.jsm:280:3
createAsyncFunction/asyncFunction@resource://gre/modules/Task.jsm:254:14
Task_spawn@resource://gre/modules/Task.jsm:168:12
this.DeferredTask.prototype._timerCallback@resource://gre/modules/DeferredTask.jsm:280:29

*************************
(Reporter)

Comment 3

a year ago
Line 497 in resource://gre/modules/LoginManagerParent.jsm is:

"    yield Services.logins.initializationPromise;"
(Reporter)

Comment 4

a year ago
Work properly when I use binary x86_64 from the mozilla site. 
Probably bug in distribution (Ubuntu/Mint)
(Reporter)

Updated

a year ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.