GNOME Bugzilla – Bug 579140
Evolution crashes when connecting to the Exchange server (OWA)
Last modified: 2009-04-21 18:40:11 UTC
Steps to reproduce: Start evolution, connect to exchange server: it asks for the password and then crashes. Evolution's main window is visible for a second, and then it disappears. Console message: 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-exchange-server stay running. For some reason, it crashed before, now it worked today in the morning, and later it started crashing again. I use evolution from Ubuntu Jaunty 9.04: evolution 2.26.1-0ubuntu1 evolution-data-server 2.26.1-0ubuntu1 evolution-exchange 2.26.0-0ubuntu2 Stack trace:
+ Trace 214502
Other information:
Created attachment 132751 [details] Full thread dump of evolution process after crash
I get this too on Arch and also on ubuntu.
Could you run evolution under gdb and when it crashes, the gdb will stop. Do "t a a bt" there (backtrace for evo), and then, before quitting gdb, on the other console/terminal, do get backtraces for evolution-data-server and evolution-exchange-storage process, say like this: $ gdb --batch --ex "t a a bt" -pid=PID &>PID.log where PID is a process ID of the running process. The best name file by the process, not by its ID. (like evo/eds/eex.log) The trace from evolution doesn't indicate the connection being used in other thread, thus it might be it's used in other process. Does it matter if you run evolution in a mail, than in an address book/calendar/... with respect to the crash? (you can run "evolution --component mail".)
Ehm, wait a minute, looking into the code itself, this seems to be related to bug #574957. Is the package with that fix available for your distribution?
jaunty doesn't have this change yet no, but it has been uploaded as a jaunty stable update and will be accepted once jaunty is flagged as stable next week
OK, I confirm that Jaunty doesn't actually have it, and manually patching libsoup and building from source does indeed eliminate the crash. I still cannot connect to the Exchange server, with which Evolution 2.24 has worked well, but this is probably another issue. *** This bug has been marked as a duplicate of 574957 ***
OK, I confirm that Jaunty doesn't actually have it, and manually patching libsoup and building from source does indeed eliminate the crash. I still cannot connect to the Exchange server, with which Evolution 2.24 has worked well, but this is probably another issue.
(In reply to comment #7) > I still cannot connect to the Exchange server, with which Evolution 2.24 has > worked well, but this is probably another issue. Thanks for the update. What's the new bug for the above? What does it complain?
No complaints from evolution, it just cannot fetch messages from the exchange server, while "Authenticate" button works when setting the account up. No useful console output as far as I can see. Will try tomorrow with E2K_DEBUG=4