Created attachment 295962 [details]
fully symbolic stack trace from evolution

Changed version to 8 from rawhide...

[jstanley@rugrat ~]$ rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n'
evolution evolution-exchange
evolution-2.12.3-1.fc8.x86_64
evolution-2.12.3-1.fc8.i386
evolution-exchange-2.12.3-1.fc8.x86_64

Thanks for the bug report.

I may be overlooking something but it looks like the stack trace does not
identify the source of the crash.  All threads appear to be idle or blocked.

If the crash is repeatable, can you post the debug output from Bug Buddy?  It
might reveal something the first stack trace didn't.

I'm not sure that it is reproducible - that crash came from a core file that got
left on my system - I can provide it if you need (it's 67MB though).  I noticed
the same thing that you did, but hoped someone smarter than me might be able to
make some sense of it. :)

The interesting thing is I've got another similar looking stack trace in bug
434900.  This may not be evolution/totem at all be rather some core GNOME thing.
 There is no bug buddy since I use XFCE as my desktop :(

Hmm, I doubt the core file would be useful.  I would just do exactly the same
thing as you did.

Just to clarify, Evolution crashed when you clicked on an /email/ about a
meeting request, not something on your calendar, correct?  I tried playing
around with Exchange server meetings but could not reproduce the crash, not
suprisingly.  This may just be one of those random crashes that Evolution is
prone to.

Setting state to NEEDINFO for the time being.  If you see this crash again and
manage to capture another stack trace, feel free to post it here.  If it happens
frequently enough, running Evolution under GDB might give a more useful stack trace.

Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

Yeah, there's no way to reproduce this that I'm aware of.  Closing.