GNOME Bugzilla – Bug 320015
Evolution/Connector crashes during Exchange server interactions
Last modified: 2008-08-08 09:58:05 UTC
Steps to reproduce: 1. Respond to an email, sit idle, change to calendar view.... sometimes these things work, sometimes not. It seems to be a random crash. 2. Connecting to corporate MS Exchange Server 2000 servers that will drop connections after a timeout period. Note that this timeout doesn't seem to be the source of crash in this case, as I have had it crash after attempting to generate an email response immediately after starting up evolution. Note that everytime I get a crash of any kind, I execute a "evolution --force-shutdown" command before restarting the application. (Crashes are frequent enough that I have an alias for it now.) Stack trace: >>> Debugging Information: >>> >>> Backtrace was generated from >>> '/usr/local:/opt/gnome:/usr/libexec/evolution-exchange-storage' >>> >>> Using host libthread_db library "/lib/tls/libthread_db.so.1". >>> [Thread debugging using libthread_db enabled] >>> [New Thread 1097867328 (LWP 26684)] >>> [New Thread 1101122480 (LWP 26685)] >>> [Thread debugging using libthread_db enabled] >>> [New Thread 1097867328 (LWP 26684)] >>> [New Thread 1101122480 (LWP 26685)] >>> [Thread debugging using libthread_db enabled] >>> [New Thread 1097867328 (LWP 26684)] >>> [New Thread 1101122480 (LWP 26685)] >>> 0xffffe410 in ?? () >>> #0 0xffffe410 in ?? () >>> #1 0xbfffd4fc in ?? () >>> #2 0x00000000 in ?? () >>> #3 0xbfffd430 in ?? () >>> #4 0x4102e13b in __waitpid_nocancel () from /lib/tls/libpthread.so.0 >>> #5 0x40624f3a in libgnomeui_segv_handle () >>> from /opt/gnome/lib/libgnomeui-2.so.0 >>> #6 <signal handler called> >>> #7 0x41040670 in g_array_free () from /opt/gnome/lib/libglib-2.0.so.0 >>> #8 0x41040724 in g_byte_array_free () from >>> /opt/gnome/lib/libglib-2.0.so.0 >>> #9 0x404ce7be in io_cleanup (msg=0x828b2a8) at soup-message-io.c:90 >>> #10 0x404ce910 in soup_message_io_finished (msg=0x828b2a8) >>> at soup-message-io.c:142 >>> #11 0x404cf87f in io_read (sock=0x8252f18, msg=0x828b2a8) >>> at soup-message-io.c:653 >>> #12 0x40fd17b1 in g_cclosure_marshal_VOID__VOID () >>> from /opt/gnome/lib/libgobject-2.0.so.0 >>> #13 0x40fc2d9b in g_closure_invoke () from >>> /opt/gnome/lib/libgobject-2.0.so.0 >>> #14 0x40fd3ca0 in signal_emit_unlocked_R () >>> from /opt/gnome/lib/libgobject-2.0.so.0 >>> #15 0x40fd5371 in g_signal_emit_valist () >>> from /opt/gnome/lib/libgobject-2.0.so.0 >>> #16 0x40fd56a2 in g_signal_emit () from >>> /opt/gnome/lib/libgobject-2.0.so.0 >>> #17 0x404dc0ee in socket_read_watch (chan=0x83e1088, cond=G_IO_IN, >>> user_data=0x8252f18) at soup-socket.c:880 >>> #18 0x4107de6f in g_io_unix_dispatch () from >>> /opt/gnome/lib/libglib-2.0.so.0 >>> #19 0x41056e87 in g_main_context_dispatch () >>> from /opt/gnome/lib/libglib-2.0.so.0 >>> #20 0x410595c7 in g_main_context_iterate () >>> from /opt/gnome/lib/libglib-2.0.so.0 >>> #21 0x4105a7b7 in g_main_loop_run () from >>> /opt/gnome/lib/libglib-2.0.so.0 >>> #22 0x40dc14d0 in bonobo_main () from /opt/gnome/lib/libbonobo-2.so.0 >>> #23 0x08079000 in main (argc=3, argv=0xbfffdef4) at main.c:225 >>> >>> Thread 2 (Thread 1101122480 (LWP 26685)): >>> #0 0xffffe410 in ?? () >>> No symbol table info available. >>> #1 0x41a1c9c8 in ?? () >>> No symbol table info available. >>> #2 0xffffffff in ?? () >>> No symbol table info available. >>> #3 0x0000000b in ?? () >>> No symbol table info available. >>> #4 0x4146a804 in poll () from /lib/tls/libc.so.6 >>> No symbol table info available. >>> #5 0x41059558 in g_main_context_iterate () >>> from /opt/gnome/lib/libglib-2.0.so.0 >>> No symbol table info available. >>> #6 0x4105a7b7 in g_main_loop_run () from >>> /opt/gnome/lib/libglib-2.0.so.0 >>> No symbol table info available. >>> #7 0x40f9c780 in link_io_thread_fn () from >>> /opt/gnome/lib/libORBit-2.so.0 >>> No symbol table info available. >>> #8 0x410732a9 in g_thread_create_proxy () from >>> /opt/gnome/lib/libglib-2.0.so.0 >>> No symbol table info available. >>> #9 0x41028a13 in start_thread () from /lib/tls/libpthread.so.0 >>> No symbol table info available. >>> #10 0x414739da in clone () from /lib/tls/libc.so.6 >>> No symbol table info available. >>> >>> Thread 1 (Thread 1097867328 (LWP 26684)): >>> #0 0xffffe410 in ?? () >>> No symbol table info available. >>> #1 0xbfffd4fc in ?? () >>> No symbol table info available. >>> #2 0x00000000 in ?? () >>> No symbol table info available. >>> #3 0xbfffd430 in ?? () >>> No symbol table info available. >>> #4 0x4102e13b in __waitpid_nocancel () from /lib/tls/libpthread.so.0 >>> No symbol table info available. >>> #5 0x40624f3a in libgnomeui_segv_handle () >>> from /opt/gnome/lib/libgnomeui-2.so.0 >>> No symbol table info available. >>> #6 <signal handler called> >>> No symbol table info available. >>> #7 0x41040670 in g_array_free () from /opt/gnome/lib/libglib-2.0.so.0 >>> No symbol table info available. >>> #8 0x41040724 in g_byte_array_free () from >>> /opt/gnome/lib/libglib-2.0.so.0 >>> No symbol table info available. >>> #9 0x404ce7be in io_cleanup (msg=0x828b2a8) at soup-message-io.c:90 >>> io = (SoupMessageIOData *) 0x83db490 >>> #10 0x404ce910 in soup_message_io_finished (msg=0x828b2a8) >>> at soup-message-io.c:142 >>> No locals. >>> #11 0x404cf87f in io_read (sock=0x8252f18, msg=0x828b2a8) >>> at soup-message-io.c:653 >>> io = (SoupMessageIOData *) 0x83db490 >>> status = 200 >>> #12 0x40fd17b1 in g_cclosure_marshal_VOID__VOID () >>> from /opt/gnome/lib/libgobject-2.0.so.0 >>> No symbol table info available. >>> #13 0x40fc2d9b in g_closure_invoke () from >>> /opt/gnome/lib/libgobject-2.0.so.0 >>> No symbol table info available. >>> #14 0x40fd3ca0 in signal_emit_unlocked_R () >>> from /opt/gnome/lib/libgobject-2.0.so.0 >>> No symbol table info available. >>> #15 0x40fd5371 in g_signal_emit_valist () >>> from /opt/gnome/lib/libgobject-2.0.so.0 >>> No symbol table info available. >>> #16 0x40fd56a2 in g_signal_emit () from >>> /opt/gnome/lib/libgobject-2.0.so.0 >>> No symbol table info available. >>> #17 0x404dc0ee in socket_read_watch (chan=0x83e1088, cond=G_IO_IN, >>> user_data=0x8252f18) at soup-socket.c:880 >>> sock = (SoupSocket *) 0x8252f18 >>> #18 0x4107de6f in g_io_unix_dispatch () from >>> /opt/gnome/lib/libglib-2.0.so.0 >>> No symbol table info available. >>> #19 0x41056e87 in g_main_context_dispatch () >>> from /opt/gnome/lib/libglib-2.0.so.0 >>> No symbol table info available. >>> #20 0x410595c7 in g_main_context_iterate () >>> from /opt/gnome/lib/libglib-2.0.so.0 >>> No symbol table info available. >>> #21 0x4105a7b7 in g_main_loop_run () from >>> /opt/gnome/lib/libglib-2.0.so.0 >>> No symbol table info available. >>> #22 0x40dc14d0 in bonobo_main () from /opt/gnome/lib/libbonobo-2.so.0 >>> No symbol table info available. >>> #23 0x08079000 in main (argc=3, argv=0xbfffdef4) at main.c:225 >>> path = 0x812c6e0 "u" >>> config_directory = 0x8129810 "XÈ\022\b" >>> offline_listener = (ExchangeOfflineListener *) 0x814f768 >>> #0 0xffffe410 in ?? () Other information:
Chaning to connector component
Kirk: I believe this customer is running on a multiprocessor machine. Can you confirm that? Also, what SP of NLD9 is he running, and exactly what versions of the evolution, ximian-connector, and libsoup?
Yes this is 64 bit multi-processor system (IBM A Pro Intellistation) NLD9 SP2 Here are the versions. He had to install these versions to fix another bug he ran into. Hopefully we can still help him? evolution‑ 2.2.3.0.200509090320‑ 0.snap.novell.0.1 ximian‑ connector‑ 2.2.2.0.200509090320‑ 0.snap.novell.0.1 libsoup‑ 2.2.4.0.200509090320‑ 0.snap.novell.0.1
The system is not 64bit it is 32 (my mistake). It is an IBM MPro with dual Intel xeon 32 bit cpu's. The evolution, connector, and libsoup are all from the evolution-snapshot and ximian-connector-snapshot red carpet channels.
libsoup-2.2.4 is the latest version available?
As per a long-ago discussion with Parag and Harish, I'm moving the soup connector bugs to the Evolution Exchange product, because I have no way of reproducing these bugs myself, so if they stay filed against libsoup, they're never going to get fixed.
*** Bug 334798 has been marked as a duplicate of this bug. ***
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME 2.22.3.