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 580706 - Crash everytime I just switch to calendars after I enable the mapi account.
Crash everytime I just switch to calendars after I enable the mapi account.
Status: RESOLVED DUPLICATE of bug 586203
Product: evolution-mapi
Classification: Applications
Component: Calendar
0.26.x
Other All
: Normal critical
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
evolution[mapi]
: 581642 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-04-29 07:35 UTC by Mattias Eriksson
Modified: 2010-06-01 14:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mattias Eriksson 2009-04-29 07:35:53 UTC
Steps to reproduce:
I use evolution-mapi 0.26.0.1 that is included in Ubuntu Jaunty. I have only recompiled it to get the debug-symbols. 
We have the latest exchange service packs on the server. However, the environment is clustered and might be configured with some swedich locale/timzone settings (I don't really know since our IT department handling this is in another country, so it is hard to get exact info).

I have run the evolution-data-server-2.26 process in gdb to produce a backtrace. 

Stack trace:
(gdb) bt
  • #0 raise
    from /lib/libc.so.6
  • #1 abort
    from /lib/libc.so.6
  • #2 __assert_fail
    from /lib/libc.so.6
  • #3 icalerror_set_errno
    from /usr/lib/libical.so.0
  • #4 icalparameter_new_tzid
    from /usr/lib/libical.so.0
  • #5 exchange_mapi_cal_util_mapi_props_to_comp
    at exchange-mapi-cal-utils.c line 775
  • #6 mapi_cal_cache_create_cb
    at e-cal-backend-mapi.c line 917
  • #7 exchange_mapi_connection_fetch_items
    at exchange-mapi-connection.c line 1201
  • #8 cache_init
    at e-cal-backend-mapi.c line 978
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6
  • #12 ??


Other information:
Also it may be interestin to have the output from inside gdb just before it died.

exchange-mapi-connection.c:172: Entering exchange_mapi_util_read_generic_stream 
Attempt to read stream for proptag 0x81E10102 
Attempt succeeded for proptag 0x00030102 (after name conversion) 
exchange-mapi-connection.c:240: Leaving exchange_mapi_util_read_generic_stream 
exchange-mapi-connection.c:172: Entering exchange_mapi_util_read_generic_stream 
Attempt to read stream for proptag 0x81B90102 
Attempt succeeded for proptag 0x00230102 (after name conversion) 
exchange-mapi-connection.c:240: Leaving exchange_mapi_util_read_generic_stream /tmp/libical-0.43/src/libical/icalerror.c:104: BADARG: Bad argument to function
/usr/lib/libical.so.0(ical_bt+0x1f) [0x7f9fc938206f]
/usr/lib/libical.so.0(icalerror_set_errno+0x7b) [0x7f9fc93822db]
/usr/lib/libical.so.0(icalparameter_new_tzid+0x6c) [0x7f9fc936f9fc]
/usr/lib/libexchangemapi-1.0.so.0(exchange_mapi_cal_util_mapi_props_to_comp+0x6ce) [0x7f9fc214b03e]
/usr/lib/evolution-data-server-1.2/extensions/libecalbackendmapi.so [0x7f9fc235c702]
/usr/lib/libexchangemapi-1.0.so.0(exchange_mapi_connection_fetch_items+0x66d) [0x7f9fc21465bd]
/usr/lib/evolution-data-server-1.2/extensions/libecalbackendmapi.so [0x7f9fc235f15d]
/usr/lib/libglib-2.0.so.0 [0x7f9fc7312ae4]
/lib/libpthread.so.0 [0x7f9fc68503ba]
/lib/libc.so.6(clone+0x6d) [0x7f9fc65bcfcd]
evolution-data-server-2.26: /tmp/libical-0.43/src/libical/icalerror.c:106: icalerror_set_errno: Försäkran "0" falsk.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7f9fb3fff950 (LWP 9244)]
0x00007f9fc6509fb5 in raise () from /lib/libc.so.6

The "Försäkran "0" falsk." translate to "Assert "0" false."
Comment 1 Suman Manjunath 2009-04-30 07:50:35 UTC
critical warning crasher.. 

  • #5 exchange_mapi_cal_util_mapi_props_to_comp
    at exchange-mapi-cal-utils.c line 775

Comment 2 Mattias Eriksson 2009-05-04 08:52:35 UTC
Do you need any more information from me to fix this? Just let me know and I'll try to help.
Comment 3 Mattias Eriksson 2009-05-05 07:52:56 UTC
Tested with the libical from the jaunty-proposed repository with the following change. 

libical (0.43-2ubuntu1) jaunty-proposed; urgency=low

  * rules:
    use -DICAL_ERRORS_ARE_FATAL=false since those lead to quite some evolution
    hangs and crashes where those should be warnings (lp: #368508)

This seems to make the crash go away, but I guess it still doesn't solve the underlying issue.

However the calendar seems to work to schedule basic meetings. Viewing other peoples busy/free information in the scheduling guide doesn't work, but I guess that is probably unrelated to this issue... 

More realated to this may be the warnings I see when opening the calendar:

exchange-mapi-connection.c:2750: Entering exchange_mapi_get_pf_folders_list libexchangemapi-Message: exchange-mapi-connection.c:2752: exchange_mapi_get_pf_folders_list: lock(connect_lock)
    OpenPublicFolder         : ecWrongServer (0x478)
libexchangemapi-Message: exchange-mapi-connection.c:2788: exchange_mapi_get_pf_folders_list: unlock(connect_lock)

exchange-mapi-connection.c:2790: Leaving exchange_mapi_get_pf_folders_list 
(evolution:30873): camel-mapi-provider-WARNING **: Could not get Public folder list..


(evolution:30873): libecal-WARNING **: e-cal.c:320: Unexpected response

(evolution:30873): libecal-WARNING **: e-cal.c:320: Unexpected response

(evolution:30873): libecal-WARNING **: e-cal.c:320: Unexpected response

(evolution:30873): libecal-WARNING **: e-cal.c:320: Unexpected response

(evolution:30873): calendar-gui-WARNING **: Couldn't find event window
Comment 4 Akhil Laddha 2009-05-07 04:20:36 UTC
*** Bug 581642 has been marked as a duplicate of this bug. ***
Comment 5 Akhil Laddha 2009-05-07 04:21:35 UTC
traces from bug 581642

<signal handler called>
No symbol table info available.
  • #4 strlen
    from /lib64/libc.so.6
  • #5 strdup
    from /lib64/libc.so.6
  • #6 icalparameter_set_cn
    from /usr/lib64/libical.so.0
  • #7 icalparameter_new_cn
    from /usr/lib64/libical.so.0
  • #8 ical_attendees_from_props
    at exchange-mapi-cal-utils.c line 507
  • #9 exchange_mapi_cal_util_mapi_props_to_comp
    at exchange-mapi-cal-utils.c line 801
  • #10 exchange_mapi_cal_util_camel_helper
    at exchange-mapi-cal-utils.c line 1293
  • #11 fetch_item_cb
    at camel-mapi-folder.c line 920
  • #12 exchange_mapi_connection_fetch_item
    at exchange-mapi-connection.c line 1385
  • #13 mapi_folder_get_message
    at camel-mapi-folder.c line 1242
  • #14 camel_folder_get_message
    at camel-folder.c line 1148
  • #15 get_message_exec
    at mail-ops.c line 1824
  • #16 mail_msg_proxy
    at mail-mt.c line 520
  • #17 ??
    from /lib64/libglib-2.0.so.0
  • #18 ??
    from /lib64/libglib-2.0.so.0
  • #19 start_thread
    from /lib64/libpthread.so.0
  • #20 clone
    from /lib64/libc.so.6

Comment 6 Matthew Woehlke 2009-06-26 15:40:21 UTC
I have the same stack trace as in comment #5. I also disagree that this is the same bug as bug 581642; this was a dereference of a *bad* but *non-NULL* pointer, in a different part in exchange_mapi_cal_util_mapi_props_to_comp.

I've added further information to bug 581642.
Comment 7 Milan Crha 2010-06-01 14:44:21 UTC
The initial crash in icalparameter_new_tzid got fixed within the patch
for bug #586203, thus I'm marking this one as a duplicate.

With respect of bug 581642, if you can reproduce with evolution-mapi 0.30.1 or later, the best with evolution-mapi git master, then please reopen it. Thanks in advance.

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