evolution crashed with SIGSEGV in camel_folder_summary_load_from_db()

Bug #414634 reported by wavded
56
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Evolution
Invalid
Undecided
Unassigned
evolution mapi
Expired
Critical
evolution-mapi (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Just opened Evolution and got this message

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Aug 16 21:43:56 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: nvidia
Package: evolution 2.27.90-0ubuntu2
ProcCmdline: evolution --component=mail
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0xb7cd7101 <camel_folder_summary_load_from_db+49>: mov 0x20(%eax),%edx
 PC (0xb7cd7101) ok
 source "0x20(%eax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 camel_folder_summary_load_from_db ()
 camel_mapi_summary_new ()
 camel_mapi_folder_new ()
 ?? ()
 ?? ()
Title: evolution crashed with SIGSEGV in camel_folder_summary_load_from_db()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
wavded (wavded) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:camel_folder_summary_load_from_db (s=0xb4153df0,
camel_mapi_summary_new (folder=0x0,
camel_mapi_folder_new (store=0x8f08278,
mapi_get_folder (store=0x8f08278,
camel_store_get_folder (store=0x8f08278,

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

Thanks for the report , are you using the owa or mapi backend there?

Changed in evolution (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Incomplete
visibility: private → public
Revision history for this message
Alex Mauer (hawke) wrote :

I got what appears to be this crash, and I am using the mapi backend.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

The trace at https://bugzilla.gnome.org/show_bug.cgi?id=588556 is similar. The upstream bug is closed as incomplete, but I now left a comment about this bug. Linking it here.

Changed in evolution (Ubuntu):
status: Incomplete → Triaged
affects: evolution (Ubuntu) → evolution-mapi (Ubuntu)
Changed in evolution:
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Comment from upstream
>>>
I would like to ask you, whether you can retest with evolution-mapi 0.30.x and
if it'll show you, then also paste here a console output before the crash,
whether it'll show some critical warnings or anything similar. Thanks in
advance.
<<<

At the moment evolution-mapi 2.30.* or greater is not present in any Ubuntu version, but it will be at some in the development release. So, setting to incomplete for now. I will leave another comment when there is a release to test with.

Changed in evolution-mapi (Ubuntu):
status: Triaged → Incomplete
Changed in evolution-mapi:
status: Unknown → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Please try if this is still an issue with the evolution-mapi package from the following PPA https://launchpad.net/~jacob/+archive/evo230 . Thanks

Changed in evolution-mapi:
importance: Unknown → Critical
Changed in evolution-mapi:
status: Incomplete → Expired
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in evolution-mapi (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.