e-addressbook-factory crashed with SIGSEGV in dbus_message_get_reply_serial()

[SB]

Binary package hint: evolution-data-server

Bug report was generates automatically. I do not know exactly what else do the devs need for this report.
Basically, I was using Evolution for the first time after the upgrade to Natty. Tried to send a test email, and got the "Problem occurred window" although Evolution was still working and I could keep on writing my email.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution-data-server 2.32.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Sat Apr 2 12:37:02 2011
ExecutablePath: /usr/lib/evolution/e-addressbook-factory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/evolution/e-addressbook-factory
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=en_US.UTF-8
 LANGUAGE=en_US:en
 LANG=he_IL.utf8
SegvAnalysis:
 Segfault happened at: 0x7f64f1f78ce5: mov 0x0(%rbp,%rdx,1),%edx
 PC (0x7f64f1f78ce5) ok
 source "0x0(%rbp,%rdx,1)" (0x00000044) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: e-addressbook-factory crashed with SIGSEGV in dbus_message_get_reply_serial()
UpgradeStatus: Upgraded to natty on 2011-04-01 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #725700, 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.