Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it. Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Also, is this crash reproducible?

Yes, the crash is reproducible.

Here is the trace:
This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/evolution 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
.
.
.
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1502800208 (LWP 22679)]
CalDAV Eplugin starting up ...

(evolution-2.8:22679): camel-WARNING **: camel_exception_get_id called with NULL parameter.
[New Thread -1517769824 (LWP 22693)]
[New Thread -1534555232 (LWP 22695)]
[New Thread -1526162528 (LWP 22694)]
[New Thread -1543042144 (LWP 22696)]
[New Thread -1551434848 (LWP 22697)]
[New Thread -1568220256 (LWP 22699)]
[New Thread -1559827552 (LWP 22698)]
[Thread -1568220256 (LWP 22699) exited]
[New Thread -1576612960 (LWP 22700)]
[Thread -1576612960 (LWP 22700) exited]
[New Thread -1568220256 (LWP 22701)]

Gtk-CRITICAL **: gtk_option_menu_set_history: assertion `GTK_IS_OPTION_MENU (option_menu)' failed
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1502800208 (LWP 22679)]
0xffffe410 in __kernel_vsyscall ()
(gdb) thread apply all bt

+ Trace 69544

I guess it's because of the G_DEBUG=fatal-criticals

Holger, to get better stack traces add following line to the /etc/make.conf

FEATURES="splitdebug"

and add -g -ggdb to your CFLAGS
and remove -fomit-frame-pointer ;)

Now recompile evolution-data-server and Evolution

Here is the new bt:

(gdb) run
Starting program: /usr/bin/evolution 
[Thread debugging using libthread_db enabled]
[New Thread -1502529872 (LWP 8986)]
CalDAV Eplugin starting up ...

(evolution-2.8:8986): camel-WARNING **: camel_exception_get_id called with NULL parameter.
[New Thread -1517392992 (LWP 9002)]
[New Thread -1525785696 (LWP 9003)]
[New Thread -1534178400 (LWP 9004)]
[New Thread -1542571104 (LWP 9005)]
[New Thread -1551000672 (LWP 9006)]
[Thread -1551000672 (LWP 9006) exited]
[New Thread -1567790176 (LWP 9008)]
[New Thread -1559397472 (LWP 9007)]
[New Thread -1576182880 (LWP 9009)]
[Thread -1576182880 (LWP 9009) exited]
[New Thread -1576182880 (LWP 9010)]

Gtk-CRITICAL **: gtk_option_menu_set_history: assertion `GTK_IS_OPTION_MENU (option_menu)' failed
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1502529872 (LWP 8986)]
0xffffe410 in __kernel_vsyscall ()
(gdb) threads apply all bt
Undefined command: "threads".  Try "help".
(gdb) thread apply all bt

+ Trace 69570

As a workaround you can run Evolution using this commandline:
G_DEBUG="" evolution


In order to get better stacktrace, we also need that you compile glib with the debug symbols, because crash happens in thread -1502529872, which looks like this:

+ Trace 70172

Hopefully, this shows where this critical message originates from.

This is a dupe of #347166. Thanks for all your hard work in debugging this problem! You'll be pleased to know it has been fixed!

*** This bug has been marked as a duplicate of 347166 ***