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

[iMac]

Trying to "decline" a calendar event in evolution. I have three Google calendars active.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evolution-data-server 3.1.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 19 12:14:49 2011
ExecutablePath: /usr/lib/evolution/e-calendar-factory
ProcCmdline: /usr/lib/evolution/e-calendar-factory
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7f12e8f4a6b0 <_dbus_watch_invalidate>: movl $0xffffffff,0x4(%rdi)
 PC (0x7f12e8f4a6b0) ok
 source "$0xffffffff" ok
 destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
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=0x7f12ee9c9ed0) at ../../dbus/dbus-transport-socket.c:83
 socket_disconnect (transport=0x7f12ee9c9ed0) at ../../dbus/dbus-transport-socket.c:987
 _dbus_transport_disconnect (transport=0x7f12ee9c9ed0) at ../../dbus/dbus-transport.c:507
 _dbus_transport_disconnect (transport=0x7f12ee9c9ed0) at ../../dbus/dbus-transport.c:498
Title: e-calendar-factory crashed with SIGSEGV in _dbus_watch_invalidate()
UpgradeStatus: Upgraded to oneiric on 2011-09-09 (10 days ago)
UserGroups: adm admin cdrom dialout dip disk floppy fuse kvm libvirtd lpadmin netdev plugdev pulse pulse-access sambashare vboxusers vde2-net video

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