evolution crashed with SIGSEGV in atk_object_get_name()

[Bruno Girin]

Binary package hint: evolution

Upgraded to Maverick Beta yesterday (using update-manager -d from a Lucid install).

The problem is intermittent and here is how it happened:
1. Opened Evolution
2. Read a few emails, marked some as read without reading (by clicking on the envelope)
3. Selected another folder (IMAP to a Gmail account)
4. Marked a message as read by clicking on the envelope next to it

Expected behaviour:
Evolution marks the message as read

Actual behaviour
Evolution froze and eventually crashed

As mentioned above, this issue is intermittent: I have marked messages as read a number of times since upgrading yesterday and it's the first time it crashes.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Sun Sep 5 09:07:10 2010
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.utf8
SegvAnalysis:
 Segfault happened at: 0x88a3b36: cmp (%edx),%ecx
 PC (0x088a3b36) ok
 source "(%edx)" (0x33746e65) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/evolution/2.30/libetable.so.0
 ?? () from /usr/lib/evolution/2.30/libetable.so.0
 atk_object_get_name () from /usr/lib/libatk-1.0.so.0
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
Title: evolution crashed with SIGSEGV in atk_object_get_name()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (bluetooth-applet:1625): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
 (polkit-gnome-authentication-agent-1:1639): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Bruno Girin (brunogirin)]

Just changed the bug from private to public as I keep having it. It doesn't look like the retracer has managed to process it yet so if someone can explain to me how I can do that manually, I'm happy to do it.