Red Hat Bugzilla – Bug 166486
evolution keeps hanging and must be killed (bt attached)
Last modified: 2007-11-30 17:11:12 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050719 Epiphany/1.6.5
Description of problem:
Evolution keeps crashing for no apparent reason.
Tenth time today.
Using Evolution talking to an Exchange server, so package may be wrong.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. It crashes by itself.
Created attachment 117966 [details]
Sorry, evolution is not crashing, it's hanging and I have to kill it.
Thanks for this report.
Please can you do an "rpm -q evolution evolution-data-server
evolution-connector" and identify the versions in use.
Does this problem occur if you run evolution outside of gdb?
The backtrace you attached looks like it was generated by starting evolution
within gdb. Unfortunately, this always hangs in the initialisation of gnome_vfs
inside the call to seteuid; I think it's a bad interraction between gdb and that
function call. So that stops the main GUI thread: thread 1 in your backtrace,
and the UI will hang. This happened when you right-clicked on an attachment.
If evolution still hangs when run outside of gdb, then it's something else, and
will need tracking down. You appear to have evolution-debuginfo installed;
please can you also install evolution-data-server-debuginfo and
evolution-connector-debuginfo. Then please can you generate a backtrace by
starting evolution outside of gdb, and try to reproduce the hang. Once
evolution has hung, please can you find the process ID of the evolution process
and attach gdb to it ("gdb attach THE_PID"). Then do a "t a a bt" and we'll see
what it's doing.
Alternatively, if it's a crash when run outside of gdb (and a hang inside due to
the above cause), then start evolution outside of gdb (with the debuginfo
packages installed) and try to crash it. If/when it crashes, bug-buddy should
launch and give you a backtrace of all threads, please save it and attach it to
(In thread 3 or your backtrace, evolution is waiting for more data from the
evolution-exchange-storage backend. So it may be that that process has hung,
though that's a hunch at this stage).
The hang occurs outside of gdb too. The reason I ran evolution from gdb because
a "pgrep evolution" shows more than one process, four I think. Which shall I
The box is fully yummed, but I'll get versions for here tomorrow.
Start by attaching to the "evolution" process: "ps ax | grep evolution" will
show the details.
Please can you also specify the exact packages you're running (it's much easier
when looking back over past bugs to know which versions we were dealing with).
yum says there is no evolution-connector-debuginfo.
evolution-data-server-debuginfo is already installed.
# rpm -q evolution evolution-data-server
Created attachment 117993 [details]
attaching to hung process
"ps ax | grep evolution" gives me the same as "pgrep evolution".
Attached is the bt for the main evolution process.
Created attachment 117994 [details]
attaching to hung process, hang 2
Another bt, this one looks a bit different (no "corrupt stack?" warning).
Aha! Looks like the problem was a dhcp server giving out the wrong ip address.
Two computers with the same ip. Fixed now, problem seems to have gone away.
OK - so this was causing a hang (rather than crash)?
Good to hear that it's working for you now. In theory we could make Evolution
more robust against this kind of network problem, but it's not a priority. With
that in mind, I'm going to close this one as WONTFIX. Feel free to reopen it if
the hang problem recurs. Thanks for all of your feedback.
Just to confirm, it was a hang, not a crash.