I recently upgraded from Firefox 3.6.5 to Firefox 4.0.1 and status updates after pressing "Sync Now" which tell you that data sync is in progress or has finished, have STOPPED appearing. How do I know whether my data has been synced or not?
More specifically even when I click Tools->Sync Now nothing happens. Also when I do a "Reset Sync" via Tools->Options->Firefox Sync, nothing happens. Meaning no progress bar appears indicating that data is being synced or has been synced, as it used to happen in earlier versions of Firefox. Is there a way to know after pressing Sync Now that my data has been synced?
Alle Antworten (4)
There is no visual representation to show that it has worked or is in progress, but if it fails you get a bar appearing at the bottom of the screen telling you that the sync failed.
If you add the Firefox Sync toolbar button to the toolbar, hovering the mouse over the button will give a tooltip showing the last date/time of the last successful sync. For details of how to add the button see https://support.mozilla.com/kb/how-do-i-customize-toolbars
i'm using 'vanilla'-firefox 5.0 upgraded from 4.0.1
after upgrading to FF-4.0.1 i did a setup of the weave-server on my homeserver (which is a debian lenny). because performace and functionality of firefox-sync was much better than Xmarks. so after weave was running and all clients updated to FF-4.0.1 i startet connecting my clients (3 for now) to my weave-server.
everything worked fine until the upgrade to FF-5.0. since FF-5.0 one of my clients does not sync any more until i stop FF and restart it again...
even if i hit 'Sync now'-Button or navigate to 'Tools-->Sync now' nothing appeares in my apache-logfiles of the weave-virtual-host logfile. only my 2 other clients (also 'vanilla'-FF 5.0 installations).
the non-working FF-5.0 is installed on a centos-box 5.5 by ld-preloading the needed 'libstdc++.so.6.0.10'... ...NOT NICE i know. ;-)
It seems that you know what you are doing so the only thing left is to open a bug with the log-file from the non working machine. Our developers will appreciate it really much. Follow the instructions from this blogpost:
i'll do that! thanks for reply!