623103 - Bookmarks and Sync are randomly duplicating bookmarks in toolbar folder and bookmark folder

Status: RESOLVED INVALID

(Firefox :: Sync, defect)

Description

[jim]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Build Identifier: Firefox/3.6.13

On 2 machines using FF & Sync, marks in toolbar folder are being added and duplicated randomly and inconsistently. 

Reproducible: Always

Comment 1

[Philipp von Weitershausen [:philikon]]

Sorry to hear that. Please follow the steps explained in https://philikon.wordpress.com/2010/12/28/bookmark-sync-issues/ to help us track down the problem. Thanks!

Comment 2

[jim]

(In reply to comment #1)
> Sorry to hear that. Please follow the steps explained in
> https://philikon.wordpress.com/2010/12/28/bookmark-sync-issues/ to help us
> track down the problem. Thanks!

Thanks for the response, frustrating as it's so inconsistent. I'll try to submit as much data as I can.

Comment 3

[Richard Newman [:rnewman]]

Are you still seeing this with either Firefox 4 or Sync 1.7 on 3.6.16?

Comment 4

[jim]

I have only updated on machine to FF 4, and I haven't been using sync as I have never corrected this problem and all my bookmarks on both machines remain terribly corrupted. I've tried to use duplicate finder plugins but they have only crashed the program. I am looking at a time consuming manual edit of my marks, as I currently have over 2000 listed!

Comment 5

[Richard Newman [:rnewman]]

(In reply to comment #4)
> I am looking at a time consuming manual edit of my
> marks, as I currently have over 2000 listed!

Have you considered restoring from a backup? Sync makes some before it modifies your bookmarks, and you can always launch Firefox against a copy of your profile from a filesystem backup.

I'm going to close this bug, assuming that it's down to one of the several fixed bookmarks bugs that we addressed over the past few months. If you experience more bookmark sync issues after you start using Sync again, please do either reopen this bug or file a new one.

Thanks!