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 574522 - Crash while authenticating to the exchange server
Crash while authenticating to the exchange server
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.25.x
Other All
: Normal critical
: ---
Assigned To: Milan Crha
Ximian Connector QA
: 576426 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-03-08 03:37 UTC by Vincent Panel
Modified: 2009-12-14 14:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
proposed eds patch (1.42 KB, patch)
2009-03-25 12:09 UTC, Milan Crha
committed Details | Review
Full thread dump of evolution process after crash (12.78 KB, text/plain)
2009-04-16 09:55 UTC, Anton Keks
  Details

Description Vincent Panel 2009-03-08 03:37:50 UTC
Steps to reproduce:
1. Create an MSExchange type account
2. Follow the wizard until you have to enter your credentials
3. Click the "authenticate" button and enter your password
4. Evolution crashes

Stack trace:
$ gdb evolution
GNU gdb 6.8-5mdv2009.1 (Mandriva Linux release 2009.1)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i586-mandriva-linux-gnu"...
(gdb) run
Starting program: /usr/bin/evolution 
[Thread debugging using libthread_db enabled]
[New Thread 0xb62a46e0 (LWP 7621)]
[New Thread 0xb33c7b90 (LWP 7695)]
[New Thread 0xb29ffb90 (LWP 7696)]
[Thread 0xb29ffb90 (LWP 7696) exited]
[New Thread 0xb29ffb90 (LWP 7699)]
[New Thread 0xb1eadb90 (LWP 7700)]
[Thread 0xb1eadb90 (LWP 7700) exited]
[Thread 0xb33c7b90 (LWP 7695) exited]
[New Thread 0xb1eadb90 (LWP 7741)]
[Thread 0xb29ffb90 (LWP 7699) exited]
e-data-server-ui-Message: Key file does not have key
'exchange:__telindus%5cid981410;auth_Basic@owa.telindus.intra_'
[New Thread 0xb29ffb90 (LWP 7768)]
[New Thread 0xb33c7b90 (LWP 7769)]
[Thread 0xb29ffb90 (LWP 7768) exited]
[New Thread 0xb29ffb90 (LWP 7770)]
[Thread 0xb33c7b90 (LWP 7769) exited]
[New Thread 0xb33c7b90 (LWP 7771)]
[Thread 0xb29ffb90 (LWP 7770) exited]
[New Thread 0xb29ffb90 (LWP 7772)]
[Thread 0xb33c7b90 (LWP 7771) exited]
[New Thread 0xb33c7b90 (LWP 7773)]
[Thread 0xb29ffb90 (LWP 7772) exited]
[New Thread 0xb29ffb90 (LWP 7774)]
[Thread 0xb33c7b90 (LWP 7773) exited]
[New Thread 0xb33c7b90 (LWP 7775)]
[Thread 0xb29ffb90 (LWP 7774) exited]
[New Thread 0xb29ffb90 (LWP 7776)]
[Thread 0xb33c7b90 (LWP 7775) exited]
e-data-server-ui-Message: Key file does not have key
'exchange:__telindus%5cid981410;auth_Basic@owa.telindus.intra_' in group
'Passwords-Exchange'
[Thread 0xb29ffb90 (LWP 7776) exited]

(evolution:7621): e-utils-WARNING **: No parent set, or default parent
available for error dialog

Program received signal SIGSEGV, Segmentation fault.
__libc_free (mem=0x656e2e63) at malloc.c:3599
3599      if (chunk_is_mmapped(p))                       /* release mmapped
memory. */
Missing debug package(s), you should install: rpm-debug-4.4.2.3-22mnb2.i586
(gdb) thread apply all bt

Thread 1 (Thread 0xb62a46e0 (LWP 7621))

  • #0 __libc_free
    at malloc.c line 3599
  • #1 IA__g_free
    at gmem.c line 190
  • #2 ep_free_proxy_host_addr
    at e-proxy.c line 138
  • #3 IA__g_slist_foreach
    at gslist.c line 743
  • #4 e_proxy_dispose
    at e-proxy.c line 228
  • #5 IA__g_object_unref
    at gobject.c line 2393
  • #6 dispose
    at e2k-context.c line 219
  • #7 IA__g_object_unref
    at gobject.c line 2393
  • #8 got_connection
    at e2k-context.c line 330
  • #9 idle_connect_result
    at soup-socket.c line 514
  • #10 connect_watch
    at soup-socket.c line 537
  • #11 g_io_unix_dispatch
    at giounix.c line 162
  • #12 IA__g_main_context_dispatch
    at gmain.c line 1814
  • #13 g_main_context_iterate
    at gmain.c line 2448
  • #14 IA__g_main_loop_run
    at gmain.c line 2656
  • #15 IA__gtk_dialog_run
    at gtkdialog.c line 1090
  • #16 e_error_run
    at e-error.c line 628
  • #17 owa_authenticate_user
    at exchange-account-setup.c line 394
  • #18 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #19 IA__g_closure_invoke
    at gclosure.c line 767
  • #20 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #22 IA__g_signal_emit
    at gsignal.c line 3034
  • #23 IA__gtk_button_clicked
    at gtkbutton.c line 1106
  • #24 gtk_real_button_released
    at gtkbutton.c line 1702
  • #25 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #26 g_type_class_meta_marshal
    at gclosure.c line 878
  • #27 IA__g_closure_invoke
  • #28 signal_emit_unlocked_R
    at gsignal.c line 3174
  • #29 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #30 IA__g_signal_emit
    at gsignal.c line 3034
  • #31 IA__gtk_button_released
    at gtkbutton.c line 1098
  • #32 gtk_button_button_release
    at gtkbutton.c line 1594
  • #33 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #34 g_type_class_meta_marshal
    at gclosure.c line 878
  • #35 IA__g_closure_invoke
  • #36 signal_emit_unlocked_R
    at gsignal.c line 3282
  • #37 IA__g_signal_emit_valist
    at gsignal.c line 2987
  • #38 IA__g_signal_emit
    at gsignal.c line 3034
  • #39 gtk_widget_event_internal
    at gtkwidget.c line 4761
  • #40 IA__gtk_propagate_event
    at gtkmain.c line 2396
  • #41 IA__gtk_main_do_event
    at gtkmain.c line 1601
  • #42 gdk_event_dispatch
    at gdkevents-x11.c line 2364
  • #43 IA__g_main_context_dispatch
    at gmain.c line 1814
  • #44 g_main_context_iterate
    at gmain.c line 2448
  • #45 IA__g_main_loop_run
    at gmain.c line 2656
  • #46 IA__gtk_main
    at gtkmain.c line 1205
  • #47 startup_wizard
    at startup-wizard.c line 97
  • #48 epl_invoke
    at e-plugin.c line 1055
  • #49 e_plugin_invoke
    at e-plugin.c line 768
  • #50 emph_event_handle
    at e-event.c line 402
  • #51 e_event_emit
    at e-event.c line 288
  • #52 e_shell_attempt_upgrade
    at e-shell.c line 914
  • #53 e_shell_construct
    at e-shell.c line 696
  • #54 e_shell_new
    at e-shell.c line 744
  • #55 idle_cb
    at main.c line 336
  • #56 main
    at main.c line 267


Other information:
Bug already reported downstream : https://qa.mandriva.com/show_bug.cgi?id=48521
Comment 1 Milan Crha 2009-03-25 12:09:55 UTC
Created attachment 131340 [details] [review]
proposed eds patch

for evolution-data-server;

There was freed structures incorrectly, in e-proxy.c. This should fix it.
Could you test it please, before I'll commit?
Comment 2 Milan Crha 2009-04-07 12:29:39 UTC
Committed to trunk. Committed revision 10201.
Comment 3 Anton Keks 2009-04-14 13:56:55 UTC
It seems that the problem is not gone, see https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/352660

Ubuntu's evolution-data-server 2.26.0-0ubuntu2 contains the patch, but evolution still crashes.
Comment 4 Milan Crha 2009-04-14 14:51:40 UTC
Anton, I wonder what backtrace is there for your issue. If it's one similar to 
GThread-ERROR **: file /build/buildd/glib2.0-2.20.0/gthread/gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...

from the ubuntu bug you gave here, then that's totally different thing than the initial one, on the first look. Without backtrace cannot tell for 100%.
Comment 5 Anton Keks 2009-04-14 18:42:31 UTC
Yes, I have the same backtrace as you have pasted.
Sorry, if it is a different problem than you fixed. Do you know if such problem already registered in Gnome bugzilla?
Comment 6 Anton Keks 2009-04-14 18:51:04 UTC
Probably this one is closer to the one people are experiencing in Ubuntu 9.04: bug 573883
Comment 7 Milan Crha 2009-04-15 07:46:32 UTC
Anton, yup, your bug seems related, at least the console message is same. But what I pasted in comment #4 is not a backtrace, it's just a console message.
Can you run evolution-data-server from gdb and when that crashes, do "t a a bt" (quotes for clarity only), and check, whether your backtrace matches the one from your bug, please? And if so, please update it in that bug, he added there only thread, not all. By the way, are you using GroupWise?
Comment 8 Anton Keks 2009-04-15 15:33:24 UTC
After updating to evolution-data-server to 2.26.1-0ubuntu1, it stopped crashing with this message.

But, unfortunately, it still doesn't work: now evolution complains that:
---
(evolution:8342): camel-exchange-provider-WARNING **: Unable to load Exchage summary for folder personal: no such table: personal

** (evolution:8342): DEBUG: EI: mail_read_notify
** (evolution:8342): DEBUG: MAIL SERVER: Count changed: 0

(evolution:8342): evolution-mail-WARNING **: Failed to refresh folders: Lost connection to Evolution Exchange backend process
---

However, evolution-data-server's process still up and running, here is the thread dump from gdb of it:


Should I open a separate bug now? Do you need the thread dump of evolution itself?

Thanks for helping anyway!
Comment 9 Milan Crha 2009-04-15 15:48:38 UTC
(In reply to comment #8)
> Should I open a separate bug now? Do you need the thread dump of evolution
> itself?

Yes please, open a new bug for your issue. Feel free to CC me there.

From the error message given in the UI, I guess it didn't crash evolution-data-server, but evolution-exchange-storage process. Try to run it on the console and/or within gdb, and place the trace of a crash to your new bug please.
Comment 10 Anton Keks 2009-04-15 15:49:47 UTC
Sorry, evolution-exchange-storage actually crashes after reading new messages for some time.

I don't get any useful output and after it has crashed, gdb doesn't want to show the backtrace (I have attached to an already running process). Is there a way to get something useful out of it? Should I run it myself instead of attaching? How to do it?

P.S. I connect to exchange server 2003, not groupwise.
Comment 11 Milan Crha 2009-04-15 16:33:36 UTC
What's the new bug number please?
Comment 12 Anton Keks 2009-04-16 06:54:36 UTC
After updating the evolution itself (not evolution-exchange-storage), I can finally read my email, so I guess these bugs are already fixed somewhere. Thanks for helping!
Comment 13 Anton Keks 2009-04-16 09:52:00 UTC
Unfortunately, the original crash is back after a day's usage:

GThread-ERROR **: file /build/buildd/glib2.0-2.20.1/gthread/gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...

Evolution's own process crashes, both evolution-data-server and evolution-exchnage-server stay running.

Last thread:
  • #0 __kernel_vsyscall
  • #1 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #2 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #3 IA__g_logv
  • #4 IA__g_log
  • #5 g_mutex_free_posix_impl
    at /build/buildd/glib2.0-2.20.1/gthread/gthread-posix.c line 171
  • #6 ??
    from /usr/lib/libsoup-2.4.so.1
  • #7 IA__g_object_unref
    at /build/buildd/glib2.0-2.20.1/gobject/gobject.c line 2421
  • #8 dispose
    at e2k-context.c line 211
  • #9 IA__g_object_unref
    at /build/buildd/glib2.0-2.20.1/gobject/gobject.c line 2393
  • #10 got_connection
    at e2k-context.c line 330
  • #11 ??
    from /usr/lib/libsoup-2.4.so.1
  • #12 ??
    from /usr/lib/libsoup-2.4.so.1
  • #13 g_io_unix_dispatch
    at /build/buildd/glib2.0-2.20.1/glib/giounix.c line 162
  • #14 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 1814
  • #15 g_main_context_iterate
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 2448
  • #16 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 2656
  • #17 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #18 main
    at main.c line 704

Comment 14 Anton Keks 2009-04-16 09:55:35 UTC
Created attachment 132746 [details]
Full thread dump of evolution process after crash
Comment 15 Milan Crha 2009-04-16 10:40:22 UTC
Anton, I appreciate your responsiveness and willingness to help, but (for the third and the last time), open new bug report for your issue please. You just stole this bug with something unrelated and I'm not going to reply on anything here since now on. I checked with your very nice detailed back trace and didn't found any opened bug for that, so new bug report is the best place. Thanks in advance.
Comment 16 Anton Keks 2009-04-16 10:50:55 UTC
The new one: http://bugzilla.gnome.org/show_bug.cgi?id=579140
Sorry, I thought this crash is related to the original one.

Comment 17 Milan Crha 2009-12-14 14:16:54 UTC
*** Bug 576426 has been marked as a duplicate of this bug. ***