evolution crashed with SIGSEGV in g_closure_invoke()

Bug #759915 reported by Alexander Kallenbach
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
Expired
Critical
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

Evolution is unusable since an upgrade to Natty (see bug #753667). Just wanted to test if something changes if I let the program run for a few minutes. Then I closed it (what before never worked, Before I always had to kill the process) what in fact worked, but I've got this error message.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution 2.32.2-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Apr 13 17:18:49 2011
ExecutablePath: /usr/bin/evolution
ProcCmdline: evolution
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9b9f98f301: mov 0xc0(%rdi),%rdi
 PC (0x7f9b9f98f301) ok
 source "0xc0(%rdi)" (0x000000c0) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/evolution/2.32/libevolution-mail.so.0
 ?? () from /usr/lib/evolution/2.32/modules/libevolution-module-mail.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: evolution crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-04-07 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Alexander Kallenbach (kallenbachalex) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 save_tree_state (ml=0x0) at message-list.c:1994
 mail_shell_view_prepare_for_quit_cb (mail_shell_view=<value optimized out>, activity=0x2a0e320) at e-mail-shell-view-private.c:416
 g_closure_invoke (closure=0x7f9ba00a87a0, return_value=0x0, n_param_values=2, param_values=0x7f9ba0394e60, invocation_hint=0x7fffa545b800) at /build/buildd/glib2.0-2.28.5/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x26214e0, emission_return=0x0, instance_and_params=0x7f9ba0394e60) at /build/buildd/glib2.0-2.28.5/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=<value optimized out>) at /build/buildd/glib2.0-2.28.5/./gobject/gsignal.c:2983

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=648396

Changed in evolution (Ubuntu):
status: New → Triaged
Changed in evolution:
importance: Unknown → Medium
status: Unknown → New
Changed in evolution:
importance: Medium → Critical
Changed in evolution:
status: New → Incomplete
visibility: private → public
Changed in evolution:
status: Incomplete → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Can you please provide us some easy steps in order to reproduce the issue? if it's still reproducible with latest packages of course.

Changed in evolution:
status: New → Incomplete
Changed in evolution (Ubuntu):
status: Triaged → Incomplete
Changed in evolution:
status: Incomplete → Expired
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in evolution (Ubuntu):
status: Incomplete → 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.