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 269595 - Crash: Gpilotd failed during hotsync
Crash: Gpilotd failed during hotsync
Status: RESOLVED DUPLICATE of bug 136010
Product: gnome-pilot
Classification: Other
Component: conduit: backup
2.0.x
Other All
: Normal major
: ---
Assigned To: JP Rosevear
Evolution QA team
: 130528 247256 269735 269863 274049 303402 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-11-17 06:02 UTC by Brooks
Modified: 2006-02-07 14:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Brooks 2004-11-17 06:02:50 UTC
Distribution: SuSE Linux 9.2 (i586)
Package: Evolution
Priority: Normal
Version: GNOME2.6. 2.0.12
Gnome-Distributor: SUSE
Synopsis: Gpilotd failed during hotsync
Bugzilla-Product: Evolution
Bugzilla-Component: Conduits
Bugzilla-Version: 2.0.12
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
Just quit.

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

Expected Results:

Same
How often does this happen?
Every time.

Additional Information:



Debugging Information:

Backtrace was generated from
'/usr/local:/opt/gnome:/usr/libexec/gpilotd'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/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)...(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 1089513472 (LWP 27835)]
(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)...0xffffe410 in ?? ()
  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 <signal handler called>
  • #7 dlp_exec
    from /usr/lib/libpisock.so.8
  • #8 dlp_ReadResourceByIndex
    from /usr/lib/libpisock.so.8
  • #9 gnome_real_pilot_conduit_backup_backup
    from /opt/gnome/lib/gnome-pilot/conduits/libbackup_conduit.so
  • #10 ___marshal_Sig1
    from /opt/gnome/lib/libgpilotdconduit.so.2
  • #11 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #12 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #13 g_signal_emitv
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #14 gnome_pilot_conduit_backup_backup
    from /opt/gnome/lib/libgpilotdconduit.so.2
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 pthread_mutex_unlock
    from /lib/tls/libpthread.so.0
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 set_callbacks



Unknown version 2.0.12 in product Evolution. Setting version to the default, "unspecified".
Unknown reporter: brooksfamily@sunflower.com, 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.

Comment 1 Gerardo Marin 2004-11-27 21:03:48 UTC
*** bug 269863 has been marked as a duplicate of this bug. ***
Comment 2 Gerardo Marin 2004-11-27 21:04:04 UTC
*** bug 269735 has been marked as a duplicate of this bug. ***
Comment 3 Gerardo Marin 2004-11-27 21:04:33 UTC
*** bug 247256 has been marked as a duplicate of this bug. ***
Comment 4 phobos 2004-11-30 09:13:13 UTC
I have this problem on Evolution 2.0.1 (SuSE Pro 9.2), and it appears
filesize related.  All the larger files like Netfront, Flashplayer and
AVGMpeg tend to cause this on sync (during the backup phase of sync),
and as soon as I move some off the system, the sync simply crashes on
the next large file.  If I have some time later I'll create some
artificial files and determine where the tipping point lies.  Rgds, P.
Comment 5 Kjartan Maraas 2005-04-16 17:59:14 UTC
*** Bug 130528 has been marked as a duplicate of this bug. ***
Comment 6 Olav Vitters 2005-05-07 20:32:03 UTC
*** Bug 303402 has been marked as a duplicate of this bug. ***
Comment 7 Olav Vitters 2005-05-07 20:32:50 UTC
*** Bug 274049 has been marked as a duplicate of this bug. ***
Comment 8 Olav Vitters 2005-05-07 20:33:58 UTC
Stracktrace also looks like bug 136010 (gnome-pilot). Bug 136010 comment 2:
"I believe it's caused by a bug in pilot-link that crashes when meet a pdb larger
than 64kb.

http://mail.gnome.org/archives/gnome-pilot-list/2004-May/msg00023.html"
Comment 9 André Klapper 2005-08-28 21:19:53 UTC
since evolution 2.0.x is not maintained/patched anymore, moving all target
milestones at least to 2.2.x.
sorry for the noise.

reassigning to vvaradhan.
Comment 10 Veerapuram Varadhan 2005-09-13 13:57:00 UTC
IMO, i think this has nothing to do with evolution conduits as it appears to be
crashing while syncing the backup conduits.  Moving this to gnome-pilot.  Feel
free to move it back here, if it is evolution related.
Comment 11 Simon Major 2005-10-28 01:35:22 UTC
Related bug 320025 has full debug symbols

http://bugzilla.gnome.org/show_bug.cgi?id=320025
Comment 12 Matt Davey 2006-01-27 09:15:22 UTC
This is a pilot-link bug, which I believe has been dealt with in
the upcoming 0.12.0 release. (pre-releases are available for testing,
but the latest official pilot-link release is not at all bug free.
The pilot-link CVS head is in better shape...)
Comment 13 Matt Davey 2006-02-07 14:19:32 UTC

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