evolution crashed with SIGSEGV

Bug #1050656 reported by michael burgos
This bug report is a duplicate of:  Bug #1036958: evolution crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
New
Undecided
Unassigned

Bug Description

Evolution chashed when clicking "check for Suported types" when using Evolution Account Assistant.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution 3.5.91-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 13 19:32:39 2012
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120902)
ProcCmdline: evolution
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe03b941af0: mov 0x8(%rax),%rdi
 PC (0x7fe03b941af0) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/libcamel-1.2.so.40
 ?? () from /usr/lib/libcamel-1.2.so.40
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: evolution crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
michael burgos (vecks) 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 this software better. This particular crash has already been reported and is a duplicate of bug #1036958, 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
Revision history for this message
michael burgos (vecks) wrote :

Please do check https://bugs.launchpad.net/bugs/1036958, it does not exist.

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

No michael,

this is not the case. You just has not the permission to access the report that is all. When the original reporter has not set it to puplic a crasher is by default private.

I know this is neasty and blocks some progress, but for now and with respect that we have in moment over 2000 open reports for Ubuntu12.10(until now) it is better to keep a dub whenever it is possible as such. I do not have the permission to access the report, too, but a try to close yours as such anyway.

Your report is not lost, it will increse the flame of the original report; as signal that this is a crasher that is hitten often, and with this a more important one.

Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Thank you for reporting!

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.