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

[Cob @FPGLaurent]

Binary package hint: evolution-data-server

Crash after click the "Contacts" button :

Unable to open address book

This address book cannot be opened. This either means that an incorrect URI was entered, or the server is unreachable.

Detailed error message: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution-data-server 2.32.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
Date: Thu Mar 10 17:25:05 2011
ExecutablePath: /usr/lib/evolution/e-addressbook-factory
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110201.2)
ProcCmdline: /usr/lib/evolution/e-addressbook-factory
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=C:fr_FR:fr:en_GB:en
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fee6e14ece5: mov 0x0(%rbp,%rdx,1),%edx
 PC (0x7fee6e14ece5) ok
 source "0x0(%rbp,%rdx,1)" (0x0000005b) 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/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_message_get_reply_serial () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
Title: e-addressbook-factory crashed with SIGSEGV in dbus_message_get_reply_serial()
UpgradeStatus: Upgraded to natty on 2011-03-10 (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.