Hi! I encountered some problems with my Tungsten T3 and multisync. Everytime I try to sync with evolution I get an segmentation fault. I tried several multisync versions (0.81, 0.82cvs) and the problem stays the same.
The debugging option showed the following error code: [remote] INFORMATION: Detected vcard to belong to AddressDB [remote] INFORMATION: converting vcard to address [remote] WARNING: Unable to translate Vcard prop BDAY to a palm entry [remote] WARNING: Unable to translate Vcard prop X-EVOLUTION-LAST-USE to a palm entry [remote] WARNING: Unable to translate Vcard prop X-EVOLUTION-USE-SCORE to a palm entry [remote] DEBUG: Ping: Mutex locked! ...repeated endlessly with a 2.4 kernel and can not be killed, with an 2.6 multisync simply exits. I tried just to disable the address syncronisation but multisync detects that my tungsten was resetted. So he tries to synchronize the addresses despite the fact that the option is disabled. Any help would be appreciated, Marc -- mailto:[EMAIL PROTECTED] | http://www.creative-sadness.de ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Multisync-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-users
