evolution-data-server crash

[Nigel Malthus]

Binary package hint: evolution-data-server

Can't say if this actually a new bug - I didn't note the details, just that the crash report thing pops up after I've closed Evolution 2.21.4.
On Hardy Heron 8.04 kernel 2.6.24-2-generic

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Dec 30 10:14:30 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/evolution/evolution-data-server-2.22
NonfreeKernelModules: cdrom
Package: evolution-data-server 2.21.4-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/evolution/evolution-data-server-2.22 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_CalFactory:1.2 --oaf-ior-fd=26
ProcCwd: /
ProcEnviron:
 PATH=/home/nbm/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: evolution-data-server
StacktraceTop:
 ?? () from /usr/lib/libedata-cal-1.2.so.6
 ?? () from /usr/lib/libedata-cal-1.2.so.6
 ?? () from /usr/lib/libedata-cal-1.2.so.6
 ?? ()
 ?? () from /usr/lib/libedata-cal-1.2.so.6
Title: evolution-data-server-2.22 crashed with signal 5
Uname: Linux bebox 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy haldaemon lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:e_cal_backend_finalize (object=0x806fe60) at e-cal-backend.c:294
e_cal_backend_contacts_finalize (object=0x806fe60) at e-cal-backend-contacts.c:966
IA__g_object_unref (_object=0x806fe60)
g_hash_table_insert_internal (hash_table=0x80504c8, key=0x8085258,
impl_CalFactory_getCal (servant=0x8055d64,

[C de-Avillez (hggdh2)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 179132, so it 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. Feel free to continue to report any other bugs you may find.