Evolution crashed with SIGSEGV in g_closure_invoke() when adding new IMAP account.

[Christian Dysthe]

I was adding a new IMAP account and when saving the account Evolution froze and had to be killed. The account was stored and working when I got Evolution opened again.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: evolution 3.10.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 6 19:26:37 2014
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2014-03-17 (20 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140317)
ProcCmdline: evolution
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f87d4358520: mov 0x18(%r14),%rdi
 PC (0x7f87d4358520) ok
 source "0x18(%r14)" (0x0000001a) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: evolution crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
mtime.conffile..etc.xdg.autostart.evolution.alarm.notify.desktop: 2014-03-19T21:38:41.179051

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1293144, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.