GNOME Bugzilla – Bug 146351
crash when synchronizing date book (calendar)
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-pilot Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: crash when synchronizing date book (calendar) Bugzilla-Product: gnome-pilot Bugzilla-Component: gpilotd Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: crash when trying to sync date book (calendar) happens no matter the sync mode (sync, from pilot or to pilot) none of the options in pilot settings (sync private records, split multi-day) make any difference, in any combination Important note: data currently in Palm came from MS Outlook 2003, this is the first sync in Linux OS: Fedora Core 2, fully updated on up2date Steps to reproduce the crash: 1. sync in MS Outlook 2. sync in linux with ecalendar conduit enabled 3. Expected Results: gnome crash window How often does this happen? every sync when this conduit is active Additional Information: please email me if you need more information ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 23:35 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-pilot". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was brunon@videotron.ca. Setting to default status "UNCONFIRMED". 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. Without a stack trace from the crash it's very hard to determine what caused the crash. Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace.
Here's the stack trace I obtained through gdb by following the instructions you provided. Is it sufficient information for you ? thanks
+ Trace 49120
Thanks for following up. It looks like this is a duplicate of 147412, so I'm reopening so I can mark it as such.
*** This bug has been marked as a duplicate of 147412 ***