GNOME Bugzilla – Bug 350515
gnome-pilot crashes while "Sycronizing web" - Tungsten E2
Last modified: 2006-08-09 07:30:32 UTC
Distribution: Slackware Slackware 10.2.0 Package: gnome-pilot Severity: Normal Version: GNOME2.14.2 unspecified Gnome-Distributor: Dropline GNOME Synopsis: gnome-pilot crashes while "Sycronizing web" - Tungsten E2 Bugzilla-Product: gnome-pilot Bugzilla-Component: conduit system Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: During HotSync - USB. When Syncronising, all functions syncronize OK until "Syncronizing web" at which point gnome-pilot crashes. Steps to reproduce the crash: 1. Connect USB (/dev/tts/USB1 in this case). 2. Open Sycronisation options in Evolution 3. Hot Sync - wait for Syncronising web to appear on the Palm. Gnome pilot quits a few seconds later. Expected Results: How often does this happen? On every occaison. Additional Information: I see that there is no conduit for syncronising the web, and this may be a contributing factor. Debugging Information: Backtrace was generated from '/usr/libexec/gnome-pilot' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225759040 (LWP 10904)] [New Thread -1242805328 (LWP 10906)] [Thread debugging using libthread_db enabled] [New Thread -1225759040 (LWP 10904)] [New Thread -1242805328 (LWP 10906)] [New Thread -1234416720 (LWP 10905)] [Thread debugging using libthread_db enabled] [New Thread -1225759040 (LWP 10904)] [New Thread -1242805328 (LWP 10906)] 0xb720f411 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 70112
Thread 3 (Thread -1234416720 (LWP 10905))
------- Bug created by bug-buddy at 2006-08-09 02:22 -------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. The good news is that there is a workaround for your problem. You can get more information here: http://bugzilla.gnome.org/show_bug.cgi?id=136010 See comment 9 in that bug for the workaround. *** This bug has been marked as a duplicate of 136010 ***