User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 Here is the failed sync log (note that I replaced my login name by [myusername]): 2009-03-31 21:56:35 Service.Main DEBUG Event: weave:service:sync:start 2009-03-31 21:56:35 Service.Main DEBUG Fetching global metadata record 2009-03-31 21:56:35 RecordMgr TRACE Importing record: https://sj-weave01.services.mozilla.com/0.3/user/[myusername]/meta/global 2009-03-31 21:56:36 Net.Resource DEBUG GET request for https://sj-weave01.services.mozilla.com/0.3/user/[myusername]/meta/global 2009-03-31 21:56:36 Net.Resource DEBUG GET request successful (200) 2009-03-31 21:56:36 Service.Main DEBUG Min supported storage version is 0.3.0 2009-03-31 21:56:36 Service.Main DEBUG Remote storage version is 0.3.0 2009-03-31 21:56:36 Service.Main DEBUG Refreshing client list 2009-03-31 21:56:36 Engine.Clients DEBUG Event: weave:engine:sync:start 2009-03-31 21:56:36 Engine.Clients DEBUG Ensuring server crypto records are there 2009-03-31 21:56:36 RecordMgr TRACE Importing record: https://sj-weave01.services.mozilla.com/0.3/user/[myusername]/crypto/clients 2009-03-31 21:56:37 Net.Resource DEBUG GET request for https://sj-weave01.services.mozilla.com/0.3/user/[myusername]/crypto/clients 2009-03-31 21:56:37 Net.Resource DEBUG GET request failed (404) 2009-03-31 21:56:37 Net.Resource DEBUG Error response: "record not found" 2009-03-31 21:56:37 RecordMgr DEBUG Failed to import record: Could not GET resource https://sj-weave01.services.mozilla.com/0.3/user/[myusername]/crypto/clients (404) 2009-03-31 21:56:37 Engine.Clients WARN Sync failed 2009-03-31 21:56:37 Engine.Clients DEBUG Event: weave:engine:sync:error 2009-03-31 21:56:37 Service.Main DEBUG Event: weave:service:sync:error 2009-03-31 21:56:37 Service.Main DEBUG Caught exception: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [IWeaveCrypto.generateRandomKey] (JS frame :: file:///home/nima/.mozilla/firefox/b9i8m7mm.normal/extensions/%7B340c2bbc-ce74-4362-90b5-7c26312808ef%7D/modules/engines.js :: SyncEngine__syncStartup :: line 274) 2009-03-31 21:56:37 Service.Main DEBUG Original exception: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [IWeaveCrypto.generateRandomKey] (JS frame :: file:///home/nima/.mozilla/firefox/b9i8m7mm.normal/extensions/%7B340c2bbc-ce74-4362-90b5-7c26312808ef%7D/modules/engines.js :: SyncEngine__syncStartup :: line 274) Reproducible: Always Steps to Reproduce: 1.Check bookmarks, tabs and hystory sync in prefs 2.Sign in 3.Sync Actual Results: Sync fails Expected Results: Sync works I have Weave 0.3.0 client I installed weave on another computer with an older firefox and weave that's still not up to date. Sync fails on both computers.

IWeaveCrypto.generateRandomKey failed. Did you fill in a passphrase? How many characters was it? Did it contain symbols, or double-byte characters?

Yes, I filled in a pasphrase. It was a mixed upper and lower letters and numbers. No special chars. I tried with another one : 12345azerty, it also fails. I cleaned all my data on the server and tried to sync again, also failed.

I tried with another fresh firefox profile and the same bookmarks I copied from the failing profil, it works. My profile must be corrupted on something that makes generateRandomKey fail, but what ? Any idea ?

Wow ! Coming back to my regular "pobably corrupted" profil, sync no works ! So here is the history : 1. Sync fails un profil A 2. Run firefox using profil B and configure weave on the same account but as a different computer 3. Run a fresh successfull sync (==>) 4. Stop firefox 5. Run firefox using profil A and do nothing 6. Automatic and manual sync works ! So it works for me but there's still a strange thing. I'll tell you if I reproduce it on thit profile or another one. Perhaps firefox and weave upgrades cased problem as I switched to FX 3.1b3 and Weave 0.3.0 in the same time keeping all my profiles.

Thanks for the additional info. The key is only created once, then stored on the server. That's why the first sequence is GET -> 404 (not found) -> generateRandomKey -> fail. When you ran a sync on profile B it created the keys on the server, so that when you returned to profile A it didn't need to. The weird thing here is that the WeaveCrypto module is loading, and seems to work in some ways, but you can't generate a key.

Oh, one idea-- Perhaps, do you have FIPS mode enabled in NSS? If so, this is a duplicate of bug 443386.

Yes it looks to be a duplicate, realy sorry for loosing your time... I used FIPS, I don't know why I activated this, probably when trying to use an eToken key, and never reverted it. Thanks for the hint !