Summary: | Kpilot crash when sync with PalmOS Zire71 (kpilot kpilotdaemon palm zire71 contact) | ||
---|---|---|---|
Product: | [Applications] kpilot | Reporter: | jesusda <jesusda> |
Component: | General | Assignee: | groot |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
jesusda
2008-03-08 21:37:46 UTC
I get the same behaviour with a Palm TX, with the same stack trace. Bugger, sorry about spamming; I just forgot to include some possibly relevant information. In my case, I'd initially synchronized using ISO-8859-15 (although I use UTF-8 everywhere), then noticed my error when the characters on the Palm were messed up. I changed kpilot to use UTF-8 also, at which point it started crashing as it found conflicts. Changing back to ISO-8859-15 does not help, nor does selecting any particular conflict resolution or sync type (I've tried quite a few combinations so far...). I've debugged this a bit, and I _think_ the crash - at least in my case - is related to the character set issues: The last name of a person on my contact list has "äjä" at the end, and this has been messed up at some stage. I removed that contact from my Palm, and changed the last name to end with "aja". kpilotDaemon still died during sync, and additional debugging output I added in AbbrowserConduit::_buildResolutionTable indicated the backup entry still existed for that contact, and that one had messed up UTF8 characters in it, with the last three letters in the name showing up as "�j??T" (unicode unknown character, j, question mark, question mark, T). I removed the entire backup DB, and was then able to sync the address book successfully. However, other names with accented characters (but not at the very end of the name) still were corrupted on the Palm. After fixing the names on the Palm and syncing, names seem to be ok on both ends. This seems to have interesting information about the bug, however this is a duplicate of bug 145983 *** This bug has been marked as a duplicate of bug 145983 *** |