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 598409 - crash with signal SIGSEGV mapi_sync_deleted
crash with signal SIGSEGV mapi_sync_deleted
Status: RESOLVED DUPLICATE of bug 595260
Product: evolution-mapi
Classification: Applications
Component: Mail
unspecified
Other Linux
: Normal critical
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2009-10-14 12:29 UTC by Fabio Durán Verdugo
Modified: 2009-10-15 02:47 UTC
See Also:
GNOME target: 2.28.x
GNOME version: 2.27/2.28


Description Fabio Durán Verdugo 2009-10-14 12:29:13 UTC 
I delete message from OWA exchange, and later I open evolution with mapi connector. 
when evolution try to sync message with a server evolution freeze and crash

Program received signal SIGSEGV, Segmentation fault.

+ Trace 218295

Thread 2838494064 (LWP 3203)

  • #0 mapi_sync_deleted
    at camel-mapi-folder.c line 744
  • #1 session_thread_proxy
    at camel-session.c line 592
  • #2 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.22.2/glib/gthreadpool.c line 265
  • #3 g_thread_create_proxy
    at /build/buildd/glib2.0-2.22.2/glib/gthread.c line 635
  • #4 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #5 clone
    from /lib/tls/i686/cmov/libc.so.6 
(gdb)
Comment 1 Akhil Laddha 2009-10-15 02:47:37 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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