432013 - GUID reset fails in BSS__getNode

Status: RESOLVED INVALID

(Firefox :: Sync, defect, P2)

Description

[Mahesh Asolkar]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9pre) Gecko/2008043004 Minefield/3.0pre
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9pre) Gecko/2008043004 Minefield/3.0pre

For the past few days, weave does not sync on my Mac. It works fine on the Linux installation. Both machines use the latest nightly version of Firefox from the trunk and 0.1.29 version of Weave.

Reproducible: Always

Steps to Reproduce:
1. Click on the weave icon
2. Click on 'Sync Now'

Actual Results:  
Weave icon turns Red with the word 'Error' beside it. Activity log shows bunch of errors. I am attaching the activity log to this bug.

Expected Results:  
Weave should sync my information as expected

Reading on forums, this symptom also occurs when the data on server is generated by an old version of Weave. To address this, I reset local and server data on all my installations of Weave, restored backed up bookmarks and enabled Weave again. Still, the one on Linux works fine, this one on Mac does not. The errors are still the same.

Comment 1

[Mahesh Asolkar]

Attachment: Weave Sync activity log that displays errors mentioned in the bug

Comment 2

[Dan Mills [:thunder]]

The Weave add-on is trying to reset the guids of all local items, but places is returning an error when trying to query which items exist.

Possibly you are missing your toolbar/menu/unfiled root(s).

Comment 3

[Mahesh Asolkar]

I'll try this in a new profile and report back. Will that help?

Comment 4

[Dan Mills [:thunder]]

it would, yes! :)

Comment 5

[Mahesh Asolkar]

Sync worked in a new profile.

I was hoping the 'Reset Client Data' in Weave preferences would clean the slate for Weave and sync as if it was a new profile, as far as Weave is concerned. Shouldn't it?

Comment 6

[Dan Mills [:thunder]]

'reset client data' changed some time ago.  It used to remove all the roots, but I changed it to remove all the *contents* of each root at some point.  So possibly you hit the reset button at some point and it never worked since?

Or, you could be dealing with places db corruption, but that is far less likely imo.

Comment 7

[Dan Mills [:thunder]]

Targeting 0.2.
We should gracefully recover from these kinds of problems.

Comment 8

[Dan Mills [:thunder]]

Punting to 0.3.

Comment 9

[Dan Mills [:thunder]]

These bugs need to be triaged, removing 0.3 milestone setting.

Comment 10

[Philipp von Weitershausen [:philikon]]

Resolving this ancient bug as invalid. The bookmarks engine has been refactored multiple times by now.