GNOME Bugzilla – Bug 598300
Crash in update_server_object, exchange_mapi_cal_util_camel_helper
Last modified: 2011-03-16 15:28:36 UTC
What were you doing when the application crashed? Distribution: Fedora release 11 (Leonidas) Gnome Release: 2.26.3 2009-07-07 (Red Hat, Inc) BugBuddy Version: 2.26.0 System: Linux 2.6.30.8-64.fc11.x86_64 #1 SMP Fri Sep 25 04:43:32 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10603901 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad Memory status: size: 1504452608 vsize: 1504452608 resident: 56299520 share: 25387008 rss: 56299520 rss_rlim: 18446744073709551615 CPU usage: start_time: 1255449067 rtime: 476 utime: 409 stime: 67 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f1eb15a3910 (LWP 26948)] [New Thread 0x7f1ec55ed910 (LWP 26911)] [New Thread 0x7f1ec73f2910 (LWP 26908)] [New Thread 0x7f1ec7df3910 (LWP 26906)] [New Thread 0x7f1ed63d3910 (LWP 26905)] [New Thread 0x7f1ed77d5910 (LWP 26900)] [New Thread 0x7f1ed81d6910 (LWP 26899)] 0x0000003679e0ea2d in waitpid () from /lib64/libpthread.so.0
+ Trace 218271
Thread 1 (Thread 0x7f1ee40107f0 (LWP 26891))
---- Critical and fatal warnings logged during execution ---- ** camel-mapi-provider **: mapi_msg_set_recipient_list: assertion `item->recipients != NULL' failed ----------- .xsession-errors --------------------- Attempt to read stream for proptag 0x37010102 Attempt succeeded for proptag 0x37010102 (after name conversion) exchange-mapi-connection.c:250: Leaving exchange_mapi_util_read_generic_stream exchange-mapi-connection.c:709: Leaving exchange_mapi_util_get_attachments exchange-mapi-connection.c:811: Entering exchange_mapi_util_get_recipients exchange-mapi-connection.c:848: Leaving exchange_mapi_util_get_recipients exchange-mapi-connection.c:272: Entering exchange_mapi_util_read_body_stream exchange-mapi-connection.c:182: Entering exchange_mapi_util_read_generic_stream Attempt to read stream for proptag 0x10130102 Attempt succeeded for proptag 0x10130102 (after name conversion) exchange-mapi-connection.c:250: Leaving exchange_mapi_util_read_generic_stream exchange-mapi-connection.c:390: Leaving exchange_mapi_util_read_body_stream libexchangemapi-Message: exchange-mapi-connection.c:1500: exchange_mapi_connection_fetch_item: unlock(connect_lock) ()();,;<@><@>,<@>,<@>,<@><@>;; exchange-mapi-connection.c:1502: Leaving exchange_mapi_connection_fetch_item Missing separate debuginfo for /usr/lib64/libtdb.so.1 Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/56/1175f4b142f66a751e5f31b5f5726780123787.debug --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml2, gtk2 and glib2 (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Distribution: Fedora release 11 (Leonidas) Gnome Release: 2.26.3 2009-07-07 (Red Hat, Inc) BugBuddy Version: 2.26.0 System: Linux 2.6.30.8-64.fc11.x86_64 #1 SMP Fri Sep 25 04:43:32 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10603901 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad Memory status: size: 1575669760 vsize: 1575669760 resident: 81534976 share: 25608192 rss: 81534976 rss_rlim: 18446744073709551615 CPU usage: start_time: 1255537001 rtime: 2233 utime: 1993 stime: 240 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fd5c8b76910 (LWP 13360)] [New Thread 0x7fd5c9577910 (LWP 13147)] [New Thread 0x7fd5cb3f2910 (LWP 13145)] [New Thread 0x7fd5cbdf3910 (LWP 13143)] [New Thread 0x7fd5d8a59910 (LWP 13142)] [New Thread 0x7fd5db6ea910 (LWP 13140)] [New Thread 0x7fd5dc0eb910 (LWP 13139)] 0x0000003679e0ea2d in waitpid () from /lib64/libpthread.so.0
+ Trace 218312
Thread 2 (Thread 0x7fd5c8b76910 (LWP 13360))
----------- .xsession-errors --------------------- exchange-mapi-connection.c:2027: Leaving exchange_mapi_get_default_folder_id exchange-mapi-connection.c:1862: Entering exchange_mapi_util_resolve_named_prop libexchangemapi-Message: exchange-mapi-connection.c:1864: exchange_mapi_util_resolve_named_prop: lock(connect_lock) libexchangemapi-Message: exchange-mapi-connection.c:1915: exchange_mapi_util_resolve_named_prop: unlock(connect_lock) exchange-mapi-connection.c:1917: Leaving exchange_mapi_util_resolve_named_prop exchange-mapi-connection.c:986: Entering exchange_mapi_util_check_restriction: folder-id DF86DE0000000004 libexchangemapi-Message: exchange-mapi-connection.c:988: exchange_mapi_util_check_restriction: libexchangemapi-Message: exchange-mapi-connection.c:1076: exchange_mapi_util_check_restriction: unlock(connect_lock) exchange-mapi-connection.c:1078: Leaving exchange_mapi_util_check_restriction exchange-mapi-connection.c:2003: Entering exchange_mapi_get_default_folder_id libexchangemapi-Message: exchange-mapi-connection.c:2005: exchange_mapi_get_default_folder_id: lock(connect_lock) libexchangemapi-Message: exchange-mapi-connection.c:2025: exchange_mapi_get_default_folder_id: unlock(connect_lock) exchange-mapi-connection.c:2027: Leaving exchange_mapi_get_default_folder_id Missing separate debuginfo for /usr/lib64/libtdb.so.1 Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/56/1175f4b142f66a751e5f31b5f5726780123787.debug --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
@ Andre, was this bug closed purposefully or my mistake ? As per comment#2, i feel it has enough symbols though it's all different from actual bug report.
Oh. Thanks :)
Downstream bug report [1] about the similar, just the invocation of mapi_folder_get_message is from camel_folder_sync_message, but otherwise it's pretty same. [1] https://bugzilla.redhat.com/show_bug.cgi?id=538862
The function is gone in latest evolution-mapi (to be 2.91.92), but it seems like some fixes in it were done for 0.30.2. I'm marking this as a duplicate of that bug. *** This bug has been marked as a duplicate of bug 620810 ***