Christoph Lukas wrote on Thu April 29, at 07:25 +0200:
> A first step might be:
> Turn on the multisync debugging
>
> export MULTISYNC_DEBUG=1; /usr/local/bin/multisync
>
> and try to sync one single entry without umlaute. If this works try
> adding one entry with umlaute and see if this really breaks things.
I get this problem myself occasionally, when I try to do something out
of the ordinary. Today I had this happen myself. I'm running multisync
0.81 and evo 1.4.6 with my S55. S55 is version 16.
Today, it was a description field which was too long for the s55.
How I fixed it:
1. debug, as above... it stops on the offending entry.
2. seek and remove said entry from evolution.
3. remove entry from phone, if it exists (but it shouldn't)
4. quit evolution.
5. ps ux | grep evolution | awk '{ print $2}' |xargs kill
that should kill wombat, which will still have evo's files open.
--- at this point you have killed evo, in case you need to hack its
local files in evolution/ ... I don't recommend this, but I've had to do
it before :-)
6. quit multisync.
7. remove .multisync/1/remoteevolutionchanges (this will be a different
file for you, so use your head on this one).
rationale here is that:
. s55 crash triggers multisync to do a full database sync anyway, so
it shouldn't need to remember the changes. right?
. the offending entry is cached in this file, even though you've
deleted it from evo, multisync keeps trying to sync it to your
s55, which crashes it.
8. repeat until you have entries which work.
Love to hear if that fixes your problem.
,dunc
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Multisync-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/multisync-users
