695077 - Two sync errors displayed at the same time

Status: RESOLVED DUPLICATE of bug 704539

(Cloud Services :: General, defect)

Description

[Kevin Brosnan [Ex-Mozilla]]

Attachment: Screenshot with two info bars

Had two bottom bars notifying me of sync errors. Not sure what the cause of this is.

Comment 1

[Kevin Brosnan [Ex-Mozilla]]

Attachment: zip of my sync logs

Most of the logs look like 

1318867687851	Sync.Service	INFO	In sync().

1318867690885	Sync.Resource	WARN	Caught unexpected exception Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.responseStatus] Stack trace: _onComplete()@resource:///modules/services-sync/resource.js:327 < innerBind()@resource://services-sync/util.js:1071 < Channel_onStopRequest()@resource:///modules/services-sync/resource.js:553 in _onComplete.

1318867690885	Sync.Resource	DEBUG	Stack trace: _onComplete()@resource:///modules/services-sync/resource.js:327 < innerBind()@resource://services-sync/util.js:1071 < Channel_onStopRequest()@resource:///modules/services-sync/resource.js:553

1318867690885	Sync.Resource	DEBUG	Caught exception Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIHttpChannel.visitResponseHeaders] Stack trace: _onComplete()@resource:///modules/services-sync/resource.js:362 < innerBind()@resource://services-sync/util.js:1071 < Channel_onStopRequest()@resource:///modules/services-sync/resource.js:553 visiting headers in _onComplete.

1318867690885	Sync.Resource	DEBUG	Stack trace: _onComplete()@resource:///modules/services-sync/resource.js:362 < innerBind()@resource://services-sync/util.js:1071 < Channel_onStopRequest()@resource:///modules/services-sync/resource.js:553

Though error-1318867994664.txt and error-1318870712642.txt have auth errors. error-1318873428687.txt has Sync.Service WARN Failed to fetch symmetric keys. Failing remote setup.

Comment 2

[Gregory Szorc [:gps]]

This is possibly fixed in bug 690170 (Firefox 10). If not, it is almost certainly fixed in bug 704539 (Firefox 11).

If you still experience the issue after upgrading, please reopen this bug.