Bug 357986 – gpilot crashes during sync

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 357986 - gpilot crashes during sync


Summary:	gpilot crashes during sync


Status:	RESOLVED DUPLICATE of bug 136010

Product:	evolution
Classification:	Applications
Component:	Do Not Use
Version:	2.6.x (obsolete)
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Veerapuram Varadhan
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-27 15:46 UTC by jcj
Modified:	2013-09-13 12:30 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description jcj 2006-09-27 15:45:22 UTC

Distribution: Slackware Slackware 10.2.0
Package: Evolution
Severity: Normal
Version: GNOME2.14.3 2.6.x
Gnome-Distributor: Dropline GNOME
Synopsis: gpilot crashes during sync
Bugzilla-Product: Evolution
Bugzilla-Component: Conduits
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



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 -1225771328 (LWP 5382)]
[New Thread -1242690640 (LWP 5387)]
[Thread debugging using libthread_db enabled]
[New Thread -1225771328 (LWP 5382)]
[New Thread -1242690640 (LWP 5387)]
[Thread debugging using libthread_db enabled]
[New Thread -1225771328 (LWP 5382)]
[New Thread -1242690640 (LWP 5387)]
[New Thread -1234302032 (LWP 5383)]
0xb720c411 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 73396

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 ??
#3 ??
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
#48 ??
#49 ??
#50 ??
#51 ??
#52 ??
#53 ??
#54 ??
#55 ??
#56 ??
#57 ??
#58 ??
#59 ??
#60 ??
#61 ??
#62 ??
#63 ??
#64 ??
#65 <signal handler called>
#66 ??
from /usr/lib/libpisock.so.8
#67 dlp_exec
from /usr/lib/libpisock.so.8
#68 dlp_ReadResourceByIndex
from /usr/lib/libpisock.so.8
#69 ??
from /usr/lib/gnome-pilot/conduits/libbackup_conduit.so
#70 ??
#71 ??
#72 ??
#73 ??
#74 ??
#75 ??
#76 ??
#77 ??
#78 ??
#79 ??
#80 ??
#81 ??
from /usr/lib/gnome-pilot/conduits/libbackup_conduit.so
#82 ??
#83 ??
#84 ??
#85 ??
#86 ??
#87 ??
#88 ??
from /usr/lib/libgobject-2.0.so.0
#89 ??
#90 ??
#91 ??
#92 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#93 ??
#94 link_unlock
from /usr/lib/libORBit-2.so.0
#95 ??
from /usr/lib/libORBit-2.so.0
#96 link_connection_ref
from /usr/lib/libORBit-2.so.0
#97 g_object_ref
from /usr/lib/libgobject-2.0.so.0
#98 g_type_value_table_peek
from /usr/lib/libgobject-2.0.so.0
#99 ??
#100 ??
from /usr/lib/libgthread-2.0.so.0
#101 ??
#102 ??
from /usr/lib/libglib-2.0.so.0
#103 ??
#104 ??
from /usr/lib/libgobject-2.0.so.0
#105 ??
#106 ??
#107 ??
from /usr/lib/libgobject-2.0.so.0
#108 ??
#109 ??
#110 ??
#111 g_value_peek_pointer
from /usr/lib/libgobject-2.0.so.0
#112 ??
#113 ??
from /usr/lib/libgpilotdconduit.so.2
#114 ??
from /usr/lib/gnome-pilot/conduits/libbackup_conduit.so
#115 ??
#116 ??
#117 gnome_pilot_conduit_file_install_db
from /usr/lib/libgpilotdconduit.so.2





------- Bug created by bug-buddy at 2006-09-27 15:46 -------

Comment 1 Elijah Newren 2006-09-27 18:03:42 UTC

Looks like the description and stack trace in bug 350515.  I'll copy the comments from there:

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: bug 136010 comment 9

*** This bug has been marked as a duplicate of 136010 ***