evolution crashed with SIGSEGV in em_junk_sa_check_junk()

Bug #234729 reported by Laurent Bonnaud
12
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

This bug contains information related to bug #234724. Therefore I will merge both bugs.

ProblemType: Crash
Architecture: i386
Date: Sat May 24 19:38:31 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: fglrx
Package: evolution 2.22.1.1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: evolution
Signal: 11
SourcePackage: evolution
StacktraceTop:
 em_junk_sa_check_junk ()
 ?? () from /usr/lib/evolution/2.22/libeutil.so.0
 ?? ()
 ?? ()
 ?? ()
Title: evolution crashed with SIGSEGV in em_junk_sa_check_junk()
Uname: Linux 2.6.24-17-rt i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin plugdev scanner staff video

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :
Changed in evolution:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:em_junk_sa_check_junk ()
?? () from /usr/lib/evolution/2.22/libeutil.so.0
?? () from /usr/lib/evolution/2.22/libeutil.so.0
?? ()
camel_junk_plugin_check_junk ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
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.

Changed in evolution:
assignee: nobody → desktop-bugs
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:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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