Evolution-exchange hangs when replying to e-mail

I can verify I have a similar problem. However, I cannot even reply to one email. This is with evolution-exchange 2.12.0-0ubuntu1 on gutsy 7.10.

I also cannot add new meeting invitations to my calendar using the "Accept" button -- I get a floating point exception as well.

My terminal output (during Reply, similar also to Accept):
-----------
$ evolution
CalDAV Eplugin starting up ...
Loading Spamassasin as the default junk plugin
** (evolution:9694): DEBUG: mailto URL command: evolution %s
** (evolution:9694): DEBUG: mailto URL program: evolution

(evolution:9694): evolution-mail-WARNING **: Failed to refresh folders: Could not open folder
BBDB spinning up...
(evolution:9694): e-data-server-DEBUG: Loading categories from "/home/darkstar62/.evolution/categories.xml"
(evolution:9694): e-data-server-DEBUG: Loaded 29 categories
Floating point exception (core dumped)

Seems I fixed my own problem. After doing an strace on evolution as it crashes, I found the last thing it does is access some icons from my icon theme. After changing my theme to something else, Evolution starts working again and no more floating-point exceptions.

Still broken. I've tried the usual deleting/recreating config files, reinstalling evolution-exchange, and completely reinstalling, but still no fix.

I can confirm that I am seeing the same issue.

$ evolution
CalDAV Eplugin starting up ...
Loading Spamassasin as the default junk plugin
** (evolution:7244): DEBUG: mailto URL command: evolution %s
** (evolution:7244): DEBUG: mailto URL program: evolution

inside eab_vcard_control_new
BBDB spinning up...

** (evolution:7244): WARNING **: bbdb: Failed to add new contact: EBookStatus returned 3

- I have configured evolution not to save new contacts to the address book (which is what I believe is causing this issue). If someone can advise where in the XML files I need to check for this option, that would be good.

Further to the above.

I again went back into evolution preferences and ticked and then deselected the option to save new contacts. This appears to have caused it to take the setting and so the issue is resolved. I no longer see this line:

** (evolution:7244): WARNING **: bbdb: Failed to add new contact: EBookStatus returned 3

So there appears to be a bug with evolution NOT respecting options in the preferences section. I did kill/restart gconfd etc to rule out a cached config. The problem was still there after reboot also.

I believe I have the same issue; attaching gdb and getting a backtrace reveals this:

#0 0x00002ac06cb597a6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00002ac06c2d677c in do_add_contact (sync=1, book=0x2aaaac23c4a0, contact=0x15c50f0, error=0x7fff40693ac8, cb=0, closure=0x0) at e-book.c:315
#2 0x00002aaab05c8414 in bbdb_do_it (book=0x2aaaac23c4a0, name=0x2aaaac1dda60 "Nanley Chery", email=0x2aaaac314610 "<email address hidden>") at bbdb.c:253
#3 0x00002aaab05c858a in bbdb_handle_reply (ep=<value optimized out>, target=0xdc5b40) at bbdb.c:125
#4 0x00002ac06b9b5e4a in epl_invoke (ep=0x6f0d20, name=0x7324a0 "bbdb_handle_reply", data=0xdc5b40) at e-plugin.c:893
#5 0x00002ac06b9b178d in e_event_emit (emp=0x704840, id=0x2ac07ca3aae8 "message.replying", target=0xdc5b40) at e-event.c:299
#6 0x00002ac07c9d5d4a in em_utils_reply_to_message (folder=0x2aaaac19f2f0, uid=0x240f980 "2442", message=0x2aaaac003000, mode=1, source=0x893130) at em-composer-utils.c:1969
#7 0x00002ac07c9d6504 in reply_to_message (folder=0x13cb9a4, uid=0x0, message=0x1, user_data=<value optimized out>) at em-composer-utils.c:1910
#8 0x00002ac07ca149f2 in mail_msgport_replied (source=<value optimized out>, cond=<value optimized out>, d=<value optimized out>) at mail-mt.c:473
#9 0x00002ac074115fd3 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#10 0x00002ac0741192dd in ?? () from /usr/lib/libglib-2.0.so.0
#11 0x00002ac0741195ea in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#12 0x00002ac06ed68346 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#13 0x000000000041690b in main (argc=<value optimized out>, argv=0x7fff40694078) at main.c:602
#14 0x00002ac0743cfb44 in __libc_start_main () from /lib/libc.so.6
#15 0x000000000040a989 in _start ()

Confirming for mail forwarding, maybe this is connected? Ubuntu 8.10 with all updates until yesterday.

With all updates as of today, this problem has disappeared.

Is this symptom still reproducible in 8.10 for anyone else?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

I still have the problem with Ubuntu 9.04. Most of the time, there is no crash but evolution hangs during very long seconds before continuing the live.

I have this message in the console at the end of the hang :

(evolution:3376): gtkhtml-editor-warning **: No Such Language

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

This happened to me today, running Karmic. Although it happens much less often now.

Thanks Adam. I assume it is hanging when trying to reply or add a contact? Can you confirm you are using the latest version 2.28.1-0ubuntu1? Thank you.

I'm terribly sorry, I've replied to the wrong "Evolution hangs" bug. :-) Please disregard my previous comment.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!