http://bugzilla.moblin.org/show_bug.cgi?id=2416 --- Comment #10 from pohly <patrick.ohly(a)intel.com&gt; 2010-01-19 00:17:48 PST --- (In reply to comment #9) The commit message you refer to implements one part of the overall solution. The aborting part was added later. I don't remember exactly why I got the 222 Alert loop, though. Only if they have local data. If they have no local data, the slow sync is done as expected. We could detect a first-time sync, but it really isn't that different from an unexpected slow sync: the user might still want to avoid the matching of items on the server by doing a refresh sync instead. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.