evolution crashed with SIGSEGV in gtk_widget_get_toplevel() - Evolution crashes when called from email-notification applet for email accounts not previously set in Evolution

[Antoine Billiau]

Binary package hint: evolution

Evolution was called by email notification applet after receiving new emails.
When Evolution was called and I tryed to get the focus on Evolution, Evolution crashed.
The emails accounts for which Evolution was called by the applet were not previously set in Evolution.
Hopes this makes sense.

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 x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 16 21:24:01 2010
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: evolution --component=mail
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.utf8
SegvAnalysis:
 Segfault happened at: 0x7f63a66ced03 <gtk_widget_get_toplevel+83>: mov 0x58(%rbx),%rax
 PC (0x7f63a66ced03) ok
 source "0x58(%rbx)" (0xaaaaaaaaaaaaab02) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 gtk_widget_get_toplevel () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_widget_has_screen () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
Title: evolution crashed with SIGSEGV in gtk_widget_get_toplevel()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Antoine Billiau (antoine-billiau)]

Using Mail Notification 5.4 and Evolution 2.30.3

Apart of this problem, Evolution is working fine and do not crash.

[Antoine Billiau (antoine-billiau)]

Tried to reproduce the crash: did not have success (which is a good thing by the way).

I am sorry for the inconvenience.

[Pedro Villavicencio (pedro)]

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.