evolution crashed when creating an imap folder

[Daniel F.]

1) Description: Ubuntu Trusty Tahr (development branch) Release: 14.04
2) evolution:
  Installed: 3.10.4-0ubuntu1
  Candidate: 3.10.4-0ubuntu1
3) Evolution crashs when creating an IMAP Folder with SIGSEGV in g_closure_invoke(), but the folder was successfuly created.
4) The folder is created but Evolution should not crash

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: evolution 3.10.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 27 17:11:30 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2013-12-30 (87 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: evolution
SegvAnalysis:
 Segfault happened at: 0x7f026e140520: mov 0x18(%r14),%rdi
 PC (0x7f026e140520) ok
 source "0x18(%r14)" (0x200000000040) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown 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: Upgraded to trusty on 2014-01-06 (79 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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.