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 596017 - Segfault When Authenticating via MAPI
Segfault When Authenticating via MAPI
Status: RESOLVED DUPLICATE of bug 571579
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.26.x
Other Linux
: Normal major
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2009-09-22 22:49 UTC by Randy Goddard
Modified: 2009-09-23 03:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Randy Goddard 2009-09-22 22:49:26 UTC
In both Ubuntu 9.04 and openSUSE 11.1, when trying to authenticate against an Exchange 2008 server using MAPI, the application segfaults.  The following backtrace, and attached core file are from Ubuntu 9.04.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f4dd2fc77f0 (LWP 26360)]
0x0000000002057200 in ?? ()

Thread 1 (Thread 0x7f4dd2fc77f0 (LWP 26360))

  • #0 ??
  • #1 krb5_cc_destroy
    from /usr/lib/libdcerpc.so.0
  • #2 ??
    from /usr/lib/libdcerpc.so.0
  • #3 ??
    from /usr/lib/libdcerpc.so.0
  • #4 ??
    from /usr/lib/libdcerpc.so.0
  • #5 ??
    from /usr/lib/libdcerpc.so.0
  • #6 ??
    from /usr/lib/libdcerpc.so.0
  • #7 ??
    from /usr/lib/libdcerpc.so.0
  • #8 ??
    from /usr/lib/libdcerpc.so.0
  • #9 ??
    from /usr/lib/libdcerpc.so.0
  • #10 talloc_free
    from /usr/lib/libdcerpc.so.0
  • #11 MAPIUninitialize
    from /usr/lib/libmapi.so.0
  • #12 exchange_mapi_connection_close
    from /usr/lib/libexchangemapi-1.0.so.0
  • #13 exchange_mapi_create_profile
    from /usr/lib/libexchangemapi-1.0.so.0
  • #14 ??
    from /usr/lib/evolution/2.26/plugins/liborg-gnome-exchange-mapi.so
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #19 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #27 ??
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #34 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #35 ??
    from /usr/lib/libglib-2.0.so.0
  • #36 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #37 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 epl_invoke
    at e-plugin.c line 1055
  • #39 e_event_emit
    at e-event.c line 288
  • #40 e_shell_attempt_upgrade
    at e-shell.c line 914
  • #41 e_shell_construct
    at e-shell.c line 696
  • #42 e_shell_new
    at e-shell.c line 744
  • #43 idle_cb
    at main.c line 336
  • #44 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #45 ??
    from /usr/lib/libglib-2.0.so.0
  • #46 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #47 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #48 main
    at main.c line 704

Comment 1 Akhil Laddha 2009-09-23 03:53:39 UTC
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.

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