evolution crashed with SIGSEGV

Bug #150580 reported by Per Lindahl
6
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: evolution

I chose "continue editing" after adding an appointment to the calendar. It hung and then crashed.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Oct 8 15:56:10 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: vmnet vmblock vmmon nvidia
Package: evolution 2.12.0-0ubuntu5
PackageArchitecture: i386
ProcCmdline: evolution --component=mail
ProcCwd: /home/per
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: evolution crashed with SIGSEGV
Uname: Linux cartman 2.6.22-12-386 #1 Sun Sep 23 17:37:35 GMT 2007 i686 GNU/Linux
UserGroups: adm admin admin appeal audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:view_response_cb (widget=0x861b320, response=ITIP_VIEW_RESPONSE_ACCEPT, data=0x8b73440) at itip-formatter.c:1762
IA__g_cclosure_marshal_VOID__INT (closure=0x8b87a80, return_value=0x0, n_param_values=2, param_values=0xbfeffc6c, invocation_hint=0xbfeffb7c,
IA__g_closure_invoke (closure=0x8b87a80, return_value=0x0, n_param_values=2, param_values=0xbfeffc6c, invocation_hint=0xbfeffb7c)
signal_emit_unlocked_R (node=0x8b71a00, detail=0, instance=0x861b320, emission_return=0x0, instance_and_params=0xbfeffc6c)
IA__g_signal_emit_valist (instance=0x861b320, signal_id=486, detail=0, var_args=0xbfeffeb0 "� /build/buildd/glib2.0-2.14.1/gobject/gsignal.c:2199

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in evolution:
importance: Undecided → Medium
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.