evolution crashed with SIGSEGV

Bug #636795 reported by Jeff Lane 
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: evolution

Was attempting to move messages between IMAP folders on a remote server with evolution when it just crapped out and crashed.

Apport fired and the rest is history.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 12 03:26:40 2010
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: evolution
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f261bbb8a78: mov (%rbx),%rdx
 PC (0x7f261bbb8a78) ok
 source "(%rbx)" (0x100000000) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/evolution/2.30/libetable.so.0
 ?? () from /usr/lib/evolution/2.30/libetable.so.0
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
Title: evolution crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Jeff Lane  (bladernr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #624096, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
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.