evolution crashed with SIGABRT

Bug #756416 reported by harrier
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

I have chosen to compose a new message using Unity3d icon in lateral panel. The compose window opened but after that evolution was blocked and crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: evolution 2.32.2-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sun Apr 10 11:35:31 2011
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110410)
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=it_IT:en
 LANG=it_IT.UTF-8
Signal: 6
SourcePackage: evolution
Stacktrace:
 #0 0x0032e416 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf86b7e4
StacktraceTop: ?? ()
Title: evolution crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
harrier (harrier77) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x0032e416 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf86b7e4
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in evolution (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
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.