Bug 129527 - Evolution crashes when receiving mail
Summary: Evolution crashes when receiving mail
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 3
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact:
: 139573 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-10 01:45 UTC by Thomas J. Baker
Modified: 2007-11-30 22:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-04-06 15:43:01 UTC
Type: ---

Attachments (Terms of Use)
bug buddy stack trace (7.89 KB, text/plain)
2004-08-10 01:46 UTC, Thomas J. Baker
no flags Details
BugBuddy-generated report on my latest crash of Evolution (14.41 KB, text/plain)
2004-11-12 19:06 UTC, Terry Hurlbut
no flags Details
backtrace w/debuginfo (90.77 KB, text/plain)
2004-11-19 20:17 UTC, Keith Iosso
no flags Details
evolution crash debug info after installing debug packages (13.90 KB, text/plain)
2004-11-30 23:47 UTC, Brian Weekes
no flags Details
Backtrace as requested on #evolution (6.73 KB, text/plain)
2004-12-01 18:09 UTC, adam.huffman
no flags Details

Description Thomas J. Baker 2004-08-10 01:45:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040625 Galeon/1.3.17

Description of problem:
Evolution crashes when retrieving email. I've got two pop accounts and
one imap and it seems like it crashes randomly when popping the
comcast account. I've sent a similiar bug report to Ximian but it got
bit bucketted as a glibc bug.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. hit the send/receive button or wait for it to happen in the background

Actual Results:  Evolution will sometimes crash

Expected Results:  It doesn't crash and just get's my email.

Additional info:

I've had this problem since upgrading to fc3t1 from fc2. I've waiting
hoping each successive release of evolution would fix the problem but
it hasn't. I was watching a bug (#127225) that I thought may be the
same thing but I'm not sure it is.

Comment 1 Thomas J. Baker 2004-08-10 01:47:00 UTC
Created attachment 102554 [details]
bug buddy stack trace

Comment 2 Thomas J. Baker 2004-08-10 01:48:51 UTC
FWIW, the ximian bug is http://bugzilla.ximian.com/show_bug.cgi?id=62693

Comment 3 Thomas J. Baker 2004-08-19 13:42:09 UTC
The latest evo doesn't fix the problem (evolution-1.5.93-2). If I
disable the single comcast pop account, the other local pop and remote
imap accounts work perfectly for days at a time. Just for kicks last
night, I enabled the comcast account and evo crashed within 5 minutes.

Comment 4 Dave Malcolm 2004-08-19 15:55:37 UTC
Thanks.  Looking at the stack trace it looks like a crash inside
camel_gethostbyname; might be related to bug #127225 (perhaps a
general problem with gethostbyname); I'll investigate further...

Comment 5 Thomas J. Baker 2004-09-07 17:44:55 UTC
I no longer have this problem. I turned back on the troublesome
account and it has been working for a few weeks now. I don't recall if
it was a glibc update or an evolution update that fixed it but it
definitely seems fixed.

Comment 6 Dave Malcolm 2004-09-07 18:02:34 UTC
Please can you specify which versions you're running in which it seems
to work:
rpm -q evolution
rpm -q glibc


Comment 7 Thomas J. Baker 2004-09-07 18:12:05 UTC
evolution- and glibc-2.3.3-47 work now but I know it was
working with the prior version of Evolution and glibc too since
glibc-2.3.3-47 was installed on 9/1/2004 and evolution on 9/6/2004.

Comment 8 Terry Hurlbut 2004-11-12 19:06:17 UTC
Created attachment 106598 [details]
BugBuddy-generated report on my latest crash of Evolution

To reproduce this on a Fedora Core 2 system after the update of the glibc
packages distributed 11/11/2004:

Start Evolution, and either:
Hit the Send/Receive button, or else:
Wait for Evolution to try to send/receive mail in the background.

This is a total blocker--I had to switch to Mozilla Mail just to keep on
transacting business. I cannot, therefore, recommend Evolution to a client if
it is subject to such breakage. The correspondence I have received before
states that glibc might be responsible in some way. Neither Ximian nor Gnome
want to admit that the problem is with their code.

Comment 9 Dave Malcolm 2004-11-16 19:36:47 UTC
*** Bug 139573 has been marked as a duplicate of this bug. ***

Comment 10 Dave Malcolm 2004-11-16 19:43:32 UTC
Although the original report is against Evolution 1.5, this looks like
a duplicate of this massively-duplicated bug against Evolution 1.4 in
Ximian's bugzilla:

I've added a link to this bug into that bug

Comment 11 Dave Malcolm 2004-11-16 19:55:18 UTC
Regarding comment #8:  I'm trying to narrow down what changes occurred
to glibc to cuase the problem.  Can you tell me when was the last time
you updated glibc before 11/11/2004 ? (and ideally, exactly which
version of the package you had installed when it was working)  What
version of the package do you now have installed?  Thank you.

Comment 13 Terry Hurlbut 2004-11-16 20:26:37 UTC
Regarding Comment #11: I don't remember when the last time was that I
updated before November 11, 2004. I *can* tell you that, in general, I
update whenever up2date says that I should. Therefore, I had the *very
last version before the update*. Before I updated, Evolution never
gave me a lick of trouble. Once I updated, Evo 1.4.6 no longer worked.
(I now use Evo 2.0.2, which was the only way I could restore Evolution

The output of command string "rpm -q glibc" (issued as root) is:


The output of command string "rpm -q glibc-common" is:


As you can see, both those version numbers are consistent.

I also have the packages glibc-devel and glibc-headers installed, and
the version number is the same. (I just checked that out with Synaptic.)

Comment 14 Dave Malcolm 2004-11-16 21:04:30 UTC
Thanks for the clarification; this is an FC2 box, right?  the last
update of glibc for FC2 was in May 2004 (glibc-2.3.3-27); the recent
update 2.3.3-27.1 contained a large number of fixes; I'm looking at
them now to see what might have caused this breakage.

Comment 15 Terry Hurlbut 2004-11-16 21:33:34 UTC
Re Comment #14, yes, that is correct: this is an FC2 box. I never had
to update glibc until recently--and that's when the trouble started.

Comment 16 Keith Iosso 2004-11-18 00:32:31 UTC
I also have been experiencing this since the last update to FC2.  I
also have Comcast as my ISP, which seems like it might be relevant. 
Until it is fixed, could it make sense to retrograde glibc?

Comment 17 Terry Hurlbut 2004-11-18 03:55:13 UTC
Re Comment #16: Either roll back your glibc *or* manage to upgrade to
Evolution 2.0.2. You'll need the following as a special devel.conf file:


[freshrpm - devel]
name=Fedora Linux $releasever - $basearch - fedora - development

Paste the above into a file called devel.conf. Either do this as root
or else run:

chown root /etc/devel.conf

Then run (as root):

yum -c /etc/devel.conf update evolution

Thirty-four RPM's later, you'll at least be able to use Evo 2.0.2 and
get past this problem.

Or, you could fall back on Mozilla Mail, which has *almost* all of
Evo's features.

Comment 18 Alexander Kain 2004-11-18 16:20:43 UTC
Just FYI, I upgraded two FC2 systems to glibc and glibc-common
2.3.3-27.1 this week. On the AMD/ACPI machine evolution broke in the
manner described above, but no bad behavior on the Intel/AMP machine.
I rolled back to plain 2.3.3-27 (no .1) by downgrading to the original
glibc* rpms off of CD1, and now evolution works again on the AMD machine.

Comment 19 David Turvene 2004-11-18 16:26:11 UTC
Yeah, I tried to upgrade using the yum config in Comment #17 and,
after 1500+ header updates, got the following:

Resolving dependencies
.............Unable to satisfy dependencies
Package openoffice.org-libs needs libdb_cxx-4.2.so, this is not available.

As a final effort, I tried to do an RPM update on evo 2.0.2 and still
got dependency failures (which I expected.)

I'm rolling glibc* back to 2.3.3-27 until I do a fork-lift upgrade to FC3.

Comment 20 Dave Malcolm 2004-11-18 19:07:21 UTC
Please, if you're seeing this bug, and haven't yet upgraded, can you
install these packages:

- evolution-debuginfo 
- glibc-debuginfo
- glibc-debuginfo-common

...and then generate a stack backtrace, and post it here.

See this link for more information about how to do this:

This would be very useful; so far the backtraces I've seen aren't with
the -debuginfo packages; with the debuginfo they should yield much
more information on what's gone wrong.   Thanks.

Comment 21 Keith Iosso 2004-11-19 20:17:16 UTC
Created attachment 107084 [details]
backtrace w/debuginfo

here is a back/stacktrace.  Dave, please let me know if it doesn't meet your

Comment 22 Brian Weekes 2004-11-30 23:47:00 UTC
Created attachment 107673 [details]
evolution crash debug info after installing debug packages

I've added an attachment of my debug info after installing the debug packages.

Comment 23 adam.huffman 2004-12-01 18:09:49 UTC
Created attachment 107726 [details]
Backtrace as requested on #evolution

Comment 24 gerardo 2005-01-10 19:33:18 UTC
From ximian bug:
After reading comments about this bug for about 2 hours, I've
concluded that there is a bug in Fedora's latest (2.3.3-27.1) upgrade
of glibc libraries. (Please read bug # 129527.)
I've upgraded the glibc, glibc-common, and glibc-headers to v2.3.3-74
from Fedora Core 3, and the bug's gone! For added confirmation, I've
re-installed the 2.3.3-27.1 version of the above  libraries, and the
bug's back.

Comment 28 John Thacker 2006-10-29 22:00:30 UTC
Changing version to correct one.  (test1 -> fc3test1, and some were filed as
test3 accidentally instead; but clearly must be fc3test1 given the date of filing.)

Comment 29 Matthew Barnes 2006-12-31 22:36:40 UTC
If this was really a glibc bug I imagine the problem has long since been fixed,
but is anyone still encountering this crash in Fedora Core 6 or later?

Comment 30 Matthew Miller 2007-04-06 15:08:57 UTC
Fedora Core 3 and Fedora Core 4 are no longer supported. If you could retest
this issue on a current release or on the latest development / test version, we
would appreciate that. Otherwise, this bug will be marked as CANTFIX one month
from now. Thanks for your help and for your patience.

Comment 31 Matthew Miller 2007-04-06 15:43:01 UTC
As I understand it, this is not an issue in current releases. Marking fixed now.
Please reopen if I'm wrong.

Note You need to log in before you can comment on or make changes to this bug.