Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Synchronisation

more options

Following the update to 29 I updated synchronisation as well removing the old account, unlinking the devices and starting anew. Sync now appears to be active; the rotation blue arrows do their stuff but nothing ever synchonises (all the option boxes are ticked to synchronise). Any ideas?

Following the update to 29 I updated synchronisation as well removing the old account, unlinking the devices and starting anew. Sync now appears to be active; the rotation blue arrows do their stuff but nothing ever synchonises (all the option boxes are ticked to synchronise). Any ideas?

Chosen solution

This was Bug 1006360, which is fixed in Firefox 30. Upgrading to Beta (or waiting two weeks) should work around the problem.

Read this answer in context 👍 0

All Replies (4)

more options

Hi Archway, Did the sync complete? If it did the blue arrow would finish. If it did not, the last case I saw it not complete the amount of bookmarks were up to 32K. It may be taking along time to sync or it might be another issue. If you did not see it complete since you posted this please: about:sync-log to see if there are any errors from the time you last synced.

Thank you

more options

Thanks for the pointer to about:sync-log. Sync is still not working - I moved a bookmark to the bookmark toolbar on Monday as a test and its still not synced to any other machine.

There are 46 error files dating back to the 19th of May. I cant upload these here - it appears txt files are not allowed, neither are pdf's and if I convert to a jpg, there are 6 pages and even single pages are too big!!!

I am happy to email one or more of the error logs and if someone is willing to interpret them to come up with a suggestion, that would be appreciated.

more options

Emailing them to me is fine. Happy to take a look.

more options

Chosen Solution

This was Bug 1006360, which is fixed in Firefox 30. Upgrading to Beta (or waiting two weeks) should work around the problem.