e-calendar-factory crashed with SIGSEGV in _dbus_watch_invalidate()

[iMac]

This one was definitely an ics accept on 3.2.1-0ubuntu1 unmodified and I didn't experience any auth issues and was not doing other things concurrently. Going to let this one report so I can forward upstream.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evolution-data-server 3.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Nov 15 12:26:04 2011
ExecutablePath: /usr/lib/evolution/e-calendar-factory
ProcCmdline: /usr/lib/evolution/e-calendar-factory
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7f5847b566b0 <_dbus_watch_invalidate>: movl $0xffffffff,0x4(%rdi)
 PC (0x7f5847b566b0) ok
 source "$0xffffffff" ok
 destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 _dbus_watch_invalidate (watch=0x0) at ../../dbus/dbus-watch.c:154
 free_watches (transport=0x7f584cb2e030) at ../../dbus/dbus-transport-socket.c:83
 socket_disconnect (transport=0x7f584cb2e030) at ../../dbus/dbus-transport-socket.c:987
 _dbus_transport_disconnect (transport=0x7f584cb2e030) at ../../dbus/dbus-transport.c:507
 _dbus_transport_disconnect (transport=0x7f584cb2e030) at ../../dbus/dbus-transport.c:498
Title: e-calendar-factory crashed with SIGSEGV in _dbus_watch_invalidate()
UpgradeStatus: Upgraded to oneiric on 2011-10-28 (17 days ago)
UserGroups: adm admin cdrom dialout dip disk fax fuse libvirtd lpadmin mythtv netdev plugdev pulse pulse-access sambashare scanner tape vboxusers vde2-net video

[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 #847578, 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.