Bug 655932 – crash emsmdb_transaction at libmapi/emsmdb.c:307

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 655932 - crash emsmdb_transaction at libmapi/emsmdb.c:307


Summary:	crash emsmdb_transaction at libmapi/emsmdb.c:307


Status:	RESOLVED DUPLICATE of bug 638821

Product:	evolution-mapi
Classification:	Applications
Component:	Mail
Version:	3.0.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mapi-maint
QA Contact:	evolution-mapi-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-08-03 21:16 UTC by Fabio Durán Verdugo
Modified:	2011-08-22 06:33 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Fabio Durán Verdugo 2011-08-03 21:16:22 UTC

After the first crash Bug 655930 open evo, click in New and crash again.

[Thread debugging using libthread_db enabled]
Core was generated by `/usr/libexec/e-addressbook-factory'.
Program terminated with signal 11, Segmentation fault.

+ Trace 228020

Thread 1 (Thread 0xb777d740 (LWP 5772))

#0 emsmdb_transaction
at libmapi/emsmdb.c line 307
#1 Release
at libmapi/IUnknown.c line 149
#2 mapi_object_release
at libmapi/mapi_object.c line 99
#3 Logoff
at libmapi/IMSProvider.c line 307
#4 disconnect
at exchange-mapi-connection.c line 182
#5 exchange_mapi_connection_finalize
at exchange-mapi-connection.c line 229
#6 g_object_unref
at gobject.c line 2734
#7 ebbm_dispose
at e-book-backend-mapi.c line 1365
#8 g_object_unref
at gobject.c line 2697
#9 e_data_book_dispose
at e-data-book.c line 883
#10 g_object_unref
at gobject.c line 2697
#11 impl_Book_close
at e-data-book.c line 771
#12 _e_gdbus_gdbus_cclosure_marshaller_BOOLEAN__OBJECT
at e-gdbus-marshallers.c line 165
#13 g_closure_invoke
at gclosure.c line 767
#14 signal_emit_unlocked_R
at gsignal.c line 3252
#15 g_signal_emit_valist
at gsignal.c line 2993
#16 g_signal_emit
at gsignal.c line 3040
#17 handle_method_call
at e-gdbus-egdbusbook.c line 3724
#18 call_in_idle_cb
at gdbusconnection.c line 4445
#19 g_idle_dispatch
at gmain.c line 4558
#20 g_main_dispatch
at gmain.c line 2441
#21 g_main_context_dispatch
at gmain.c line 3014
#22 g_main_context_iterate
at gmain.c line 3092
#23 g_main_loop_run
at gmain.c line 3300
#24 main
at e-data-book-factory.c line 686

Comment 1 Fabio Durán Verdugo 2011-08-03 21:17:36 UTC

maybe this is related or dup -> bug 638821

Comment 2 Milan Crha 2011-08-05 17:13:35 UTC

I believe that this is fixed by bug #638821, thus I'm marking this as a duplicate. Note that this might also require a fix in OpenChange, as noted there.

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

Comment 3 Milan Crha 2011-08-22 06:33:51 UTC

Similar downstream bug report from 3.0.2 and e-calendar-factory:
https://bugzilla.redhat.com/show_bug.cgi?id=732315