evolution-calendar-factory crashed with SIGSEGV in soup_socket_connect_sync()

[Clownfishy]

Appeared when the screen saver kicked in.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evolution-data-server 3.10.3-0ubuntu1~saucy1 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
Date: Fri Jan 24 12:00:30 2014
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationDate: Installed on 2013-07-22 (185 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6f49ad9: mov 0x50(%eax),%eax
 PC (0xb6f49ad9) ok
 source "0x50(%eax)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libsoup-2.4.so.1
 soup_socket_connect_sync () from /usr/lib/i386-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/i386-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/i386-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/i386-linux-gnu/libsoup-2.4.so.1
Title: evolution-calendar-factory crashed with SIGSEGV in soup_socket_connect_sync()
UpgradeStatus: Upgraded to saucy on 2013-10-18 (97 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Ubuntu GNOME (ug-bot)]

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 #1202850, 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.