Hi,

> > I am successfully using multisync several month now even with entries
> > with umlaute. I am using a CVS version of multisync which is not very up
> > to date. 
> 
> Hmm.... is any developer of Multisync reading this? 

Yes all of them. :-)

> Would be interesting
> to know if there has something changed in the CVS recently. Anyway, when
> I find time, I'll try out the CVS version.

This seems to be a misunderstanding. I am using a version from CVS which
is older than 0.82.

> > Which version of evolution are you using? Probably the evolution side
> > changed? I am using evolution 1.4.5, S55 SW-Version 11.
> 
> This is Evolution 1.4.6 (Red Carpet Subscriber version), S55 SW-Version
> 16.
> 
> > Syncing about cable and bluetooth is working here.
> 
> Strange. What kernel version and version of BlueZ are you using? Or are
> you using another Bluetooth stack? Being able to write C/C++, I'm
> willing to debug this, but since I know nothing about how Bluetooth
> works in the inside I'm a bit lost (I can imagine that even if I try to
> see when it fails, it may be several buffers ahead, so I'm afraid I
> won't be able to spot the exact message which causes the phone to shut
> down).

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.

Christoph



-------------------------------------------------------
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

Reply via email to