evolution crashed with SIGSEGV in g_closure_invoke()

Bug #663825 reported by Guillaume PARIS on 2010-10-20
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
Expired
Critical
evolution (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: evolution

crash when i was reading my calendar

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu6
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CheckboxSubmission: d6ef0fe188cbc2404c052a65314f7021
CheckboxSystem: 8cd4dc6853a6c6d5209a8efe29b4d1d5
Date: Wed Oct 20 13:31:06 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.utf8
SegvAnalysis:
 Segfault happened at: 0x14b94b1: mov (%edx),%ecx
 PC (0x014b94b1) ok
 source "(%edx)" (0x7f7f7f7f) 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/libevolution-calendar.so.0
 ?? () from /usr/lib/evolution/2.30/libevolution-calendar.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: evolution crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare uucp www-data

StacktraceTop:
 ewv_pass_gdkevent_to_etext (
 e_week_view_on_motion (widget=0xaa138a0, mevent=0x9b24a00,
 _gtk_marshal_BOOLEAN__BOXED (closure=0xa0a8268,
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0

Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Pedro Villavicencio (pedro) wrote :

is that a public calendar? it looks like bug https://bugzilla.gnome.org/show_bug.cgi?id=623612 but upstream needs a calendar to be able to reproduce the issue. if it doesn't have personal info , could you please share it ? Thanks.

visibility: private → public
Changed in evolution (Ubuntu):
status: New → Incomplete
Changed in evolution:
importance: Unknown → Critical
status: Unknown → New

Sorry, it have personal data in this calendar i cannot share it.
But if I reproduce this bug another time I will try to put the procedure to it.

Thanks

Pedro Villavicencio (pedro) wrote :

any news about it? could you reproduce it with a no personal calendar?

Changed in evolution:
status: New → Expired
Jörg Frings-Fürst (jff-de) wrote :

10.10 is not longer supported
change status to invalid (see gnome-bugs)

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

Other bug subscribers

Remote bug watches

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