evolution crashed with SIGSEGV in g_object_set()

Bug #622492 reported by Chris Halse Rogers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

When running under Unity, evolution will sometimes crash, not always with an obvious trigger.

This particular crash was triggered by hitting the “Reply” button on an email. The compose window came up, but none of the window contents were rendered - it was an entirely blank grey window. At this point the whole UI was blocked - neither the compose window nor the main Evolution mail window responded, and eventually crashed.

I suspect appmenu, given its appearance in the stacktrace.

I've only attached the reduced report because (a) I've got almost all the relevant dbgsym packages installed, and (b) Launchpad doesn't accept 850MB core dumps.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.2-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.35-17.23-generic 2.6.35.2
Uname: Linux 2.6.35-17-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 23 10:04:21 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100817)
ProcCmdline: evolution
ProcEnviron:
 SHELL=/usr/bin/zsh
 LANGUAGE=en_AU:en_GB:en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fd976303e0f <g_object_set+111>: cmpq $0x50,(%rax)
 PC (0x7fd976303e0f) ok
 source "$0x50" ok
 destination "(%rax)" (0x00000415) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 g_object_set (_object=0xa6d9100,
 show_local_notify (proxy=<value optimised out>,
 g_closure_invoke (closure=0xa6dbc30,
 signal_emit_unlocked_R (node=0x2363980,
 g_signal_emit_valist (instance=0x25f41e0,
Title: evolution crashed with SIGSEGV in g_object_set()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sbuild

Revision history for this message
Chris Halse Rogers (raof) wrote :
description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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.

Changed in evolution (Ubuntu):
importance: Undecided → Medium
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.