427040 - Exception caught in WeaveLockWrapper: Keyring does not contain a key for this user

Status: RESOLVED FIXED

(Cloud Services :: General, defect, P1)

Description

[Sigurd Foshaug]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9pre) Gecko/2008040404 Minefield/3.0pre
Build Identifier: 3.0pre 2008040404, Weave version 0.1.29

When trying to sync after removing client data I get the following error: 

2008-04-04 16:09:17	Chrome.Wizard	INFO	Verifying login
2008-04-04 16:09:17	Chrome.Wizard	INFO	Adding user login/password to password manager
2008-04-04 16:09:17	Service.Main	INFO	Logging out
2008-04-04 16:09:17	Chrome.Wizard	INFO	Logged out
2008-04-04 16:09:19	Chrome.Wizard	INFO	Login verified
2008-04-04 16:09:19	Chrome.Window	INFO	Login successful
2008-04-04 16:09:20	Chrome.Wizard	INFO	Showing initialization page
2008-04-04 16:09:22	Chrome.Wizard	INFO	Sync started
2008-04-04 16:09:23	Service.BmkEngine	INFO	Beginning sync
2008-04-04 16:09:25	Service.BmkEngine	INFO	Got status file from server
2008-04-04 16:09:25	Chrome.Wizard	INFO	Sync failed
2008-04-04 16:09:26	Async.Generator	ERROR	Exception caught in WeaveLockWrapper: Keyring does not contain a key for this user
2008-04-04 16:09:30	Chrome.Wizard	INFO	Shutting down setup wizard

Reproducible: Always

Steps to Reproduce:
1.Open Firefox 
2.Verify that I am signed in to Weave
3.Click the sync button
Actual Results:  
Get a red weave sync icon in the bottom left with the word error next to it. 
History or bookmarks are not synced. 

Expected Results:  
Bookmarks and history should be synced, and a progress bar would show next to the weave icon.

Comment 1

[Jaime Mitchell (use [e-mail] for email)]

I can confirm this with 0.1.29 when trying to synch onto a second PC (20080410 trunk build as first pc which was fine and beta 5 on the second pc). 

Selecting the option to delete all user data on the server, resynchronising on the first pc and then syncing on the second pc resolved this error for me.

Comment 2

[Dan Mills [:thunder]]

Does this problem happen if you restart the browser after clearing client/server data, but before doing a first sync?  I think this bug is related to bug 424468.

Targeting 0.2.

Comment 3

[Dan Mills [:thunder]]

Fixed in revision c96d7f7f0348.