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

[zvaral]

Binary package hint: evolution-data-server

After logging in, I get this crash to report. This bug may have some relations to bugs
#725700
#715747
#719581

but I did not have to do anything (open evolution or addressbook, etc.) just log in.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution-data-server 2.32.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.37-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 24 09:48:47 2011
ExecutablePath: /usr/lib/evolution/e-addressbook-factory
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: /usr/lib/evolution/e-addressbook-factory
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe02ae9ece5: mov 0x0(%rbp,%rdx,1),%edx
 PC (0x7fe02ae9ece5) ok
 source "0x0(%rbp,%rdx,1)" (0x000000d1) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
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-03-16 (7 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.

[zvaral (z-varallyay)]

This issue is disappeared with the updates received today.