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 146351 - crash when synchronizing date book (calendar)
crash when synchronizing date book (calendar)
Status: RESOLVED DUPLICATE of bug 147412
Product: gnome-pilot
Classification: Other
Component: gpilotd
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-05 14:38 UTC by Bruno Navert
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Bruno Navert 2004-07-09 03:35:47 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.

Comment 1 Elijah Newren 2004-07-09 21:21:41 UTC
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.
Comment 2 Bruno Navert 2004-08-05 13:48:56 UTC
Here's the stack trace I obtained through gdb by following the instructions you
provided. Is it sufficient information for you ? thanks

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 raise
    from /lib/tls/libc.so.6
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_string_erase
    from /usr/lib/libglib-2.0.so.0
  • #10 _g_log_fallback_handler
    from /usr/lib/libglib-2.0.so.0
  • #11 g_log_default_handler
    from /usr/lib/libglib-2.0.so.0
  • #12 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #13 g_log
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
    from /usr/lib/gnome-pilot/conduits/libecalendar_conduit.so
  • #15 ??
    from /usr/lib/gnome-pilot/conduits/libecalendar_conduit.so
  • #16 ??
  • #17 ??
    from /usr/lib/gnome-pilot/conduits/libecalendar_conduit.so
  • #18 ??
    from /usr/lib/gnome-pilot/conduits/libecalendar_conduit.so
  • #19 ??
  • #20 ??
  • #0 ??

Comment 3 Elijah Newren 2004-08-05 14:38:08 UTC
Thanks for following up.  It looks like this is a duplicate of 147412, so I'm
reopening so I can mark it as such.
Comment 4 Elijah Newren 2004-08-05 14:38:22 UTC

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