Bug 158983 - Kpilot crash when sync with PalmOS Zire71 (kpilot kpilotdaemon palm zire71 contact)
Summary: Kpilot crash when sync with PalmOS Zire71 (kpilot kpilotdaemon palm zire71 co...
Status: RESOLVED DUPLICATE of bug 145983
Alias: None
Product: kpilot
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: groot
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-08 21:37 UTC by jesusda
Modified: 2008-12-05 02:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jesusda 2008-03-08 21:37:46 UTC
Version:            (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When sync, kpilot crashes because some contacts differs from KAddressbook.


(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb66cf6c0 (LWP 27238)]
[New Thread 0xb64dab90 (LWP 27239)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0xb583d4df in AbbrowserConduit::_buildResolutionTable ()
   from /usr/lib/kde3/conduit_address.so
#6  0xb583e762 in AbbrowserConduit::_smartMergeAddressee ()
   from /usr/lib/kde3/conduit_address.so
#7  0xb583eeab in AbbrowserConduit::syncAddressee ()
   from /usr/lib/kde3/conduit_address.so
#8  0xb583f5e7 in AbbrowserConduit::slotPalmRecToPC ()
   from /usr/lib/kde3/conduit_address.so
#9  0xb583f7f4 in AbbrowserConduit::qt_invoke ()
   from /usr/lib/kde3/conduit_address.so
#10 0xb71c600d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb74f01be in QSignal::signal () from /usr/lib/libqt-mt.so.3
#12 0xb71e1967 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#13 0xb71e8a33 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#14 0xb71681ca in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#15 0xb7168fb6 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#16 0xb6ea8ec2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#17 0xb715d5ae in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#18 0xb7117388 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#19 0xb717ebc0 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#20 0xb717ea56 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#21 0xb7167d3f in QApplication::exec () from /usr/lib/libqt-mt.so.3
#22 0x080589a3 in ?? ()
#23 0xbf82a130 in ?? ()
#24 0x08071958 in ?? ()
#25 0x00000001 in ?? ()
#26 0x00000000 in ?? ()
Comment 1 Tomi Junnila 2008-04-01 22:12:30 UTC
I get the same behaviour with a Palm TX, with the same stack trace.
Comment 2 Tomi Junnila 2008-04-01 22:26:27 UTC
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...).
Comment 3 Tomi Junnila 2008-04-02 18:13:20 UTC
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.
Comment 4 Dario Andres 2008-12-05 02:43:29 UTC
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 ***