8:41 p.m.
On Thu, Mar 11, 2010 at 12:40:15PM +0800, Chen, Congwu wrote:
Could you try with syncevolution n900 addressbook, if that still
fails, could you send me the log file for me to investigate?
So, to add some more context, here is a sample summary of a "regular"
execution of "syncevolution n900":
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| item(s) in database backup: 1490 before sync, 1490 after it |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| memo | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| todo | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Thu Mar 11 10:33:52 2010, duration 1:34min |
| synchronization completed successfully |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
If I try, as you suggested, "syncevolution n900 addressbook" I re-got a
"Underlying transport error":
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Thu Mar 11 10:37:42 2010, duration 0:00min |
| external transport failure (local, status 20043) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: ObexTransprotAgent: Underlying transport error
I get the same replacing on the command line "Contacts" for
"addressbook". I'll follow-up in private mail the error log.
I am not sure either.. Anyway if your calendar syncs well with no
warnings like "rejected items", I think you don't need the 'super'
(or
combined calendar and todo) stuff.
OK, thanks, I indeed get no "rejected items".
No, do you already have the same events on your N900? A first time
sync between two parties has to be "slow sync" and if items was
already in both party, it is possible you end up with a lot of
duplicates.
I had indeed some events on the N900 calendar---arrived there via the
migration from my old phone to this one---but the one that actually got
duplicated were not on the N900 calendar. I've obtained duplicates of
new events that were only on evolution, with no evident pattern to me.
How can I do a new "slow sync" to re-bootstrap the process? Ideally I
can just delete all events on the N900 and re-sync, but I obviously fear
that the sync will consequently delete all events from my evolution,
which wouldn't be nice :-) Ideally I want to re-start from scratch with
an evolution -> N900 sync, but I don't know how to (safely) achieve
that.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack(a){upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime