GNOME Bugzilla – Bug 274458
Crash: Syncronizing Palm. Conduit Backup
Last modified: 2006-03-13 22:53:37 UTC
Distribution: Debian 3.1 Package: Evolution Priority: Major Version: GNOME2.8.3 2.0.12 Gnome-Distributor: Debian Synopsis: Syncronizing Palm. Conduit Backup Bugzilla-Product: Evolution Bugzilla-Component: Conduits Bugzilla-Version: 2.0.12 BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Description of the crash: When I start synchronizing my palm, synchronizing starts ok. When my Palm comes to "Synchronizing J9 MIDP Bundle", a message pops up about "gpalmd" has crashed. Then the palm stops synchronizing and times out after a while. J9 is IBM's smal size java virtual machine. I use: GNOME from Debian Linux testing/sid Linux kernel 2.6.10-1-k7 from Debian. Evolution 2.0.4 gnome-pilot-panelprogram 2.0.12 (swedish text) I have a Palm Tungsten T3 with PalmOS v.5.2.1 It's connected with USB cradle This is information about J9 on my Palm: IBM Java VM v.2.1.008 37k J9 Java Launcher v.2.1 721k J9 MIDP Bundle v.2.1 861k On my palm log I can see version of gnome-pilot "gnome-pilot v.2.0.12" and last back up in the palm sync log was "MMIDCache 1" backed up Steps to reproduce the crash: 1. Set up palm-pilot-panelprogram from Evolution 2. Start sync from palm 3. Look when crach message comes up Expected Results: Everything on Palm backed up/syncronisized and no crash message. How often does this happen? Everytime I syncronisize my Palm Additional Information: When I unselect Backup conduit in Evolution, everything works ok (except Backup databases on palm ;-) Somthing I missed? Debugging Information: Backtrace was generated from '/usr/bin/gpilotd' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) [Thread debugging using libthread_db enabled] [New Thread -1221446240 (LWP 9751)] [New Thread -1239565392 (LWP 10206)] [New Thread -1231176784 (LWP 10205)] (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) (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) 0x4117d511 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 57796
Thread 1 (Thread -1221446240 (LWP 9751))
Unknown version 2.0.12 in product Evolution. Setting version to the default, "unspecified". Unknown reporter: anders.jackson@minpost.nu, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Ok, i'll try. Which libraries do you need debug information from? Debian only got for libglib2.0.0 and libgtk2.0.0 (at least what I found out). I could compile some more, if you could tell which is needed (don't have time or CPU cyckles to do them all ;-) Yours Anders Jackson
*** Bug 304907 has been marked as a duplicate of this bug. ***
Appears to be a duplicate of the >64k segment pilot-link bug. *** This bug has been marked as a duplicate of 136010 ***