evolution crashed with SIGSEGV in imapx_parse_capability()

Bug #1502648 reported by Dave
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)

Bug Description

After upgrade from gnome ubuntu 15.04 to gnome ubuntu 15.10, evolution crashes.
There are several imap settings defined over online accounts, a google account and an exchange account.

Crash occures on imap.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: evolution 3.16.5-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Oct 4 17:58:47 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2015-09-27 (7 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: evolution
 PATH=(custom, no user)
 Segfault happened at: 0x7f59a9b3d313 <imapx_parse_capability+659>: movzbl (%rsi),%edx
 PC (0x7f59a9b3d313) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
 imapx_parse_capability () from /usr/lib/evolution-data-server/camel-providers/libcamelimapx.so
 imapx_parse_status () from /usr/lib/evolution-data-server/camel-providers/libcamelimapx.so
 ?? () from /usr/lib/evolution-data-server/camel-providers/libcamelimapx.so
 ?? () from /usr/lib/evolution-data-server/camel-providers/libcamelimapx.so
 imapx_connect_to_server () from /usr/lib/evolution-data-server/camel-providers/libcamelimapx.so
Title: evolution crashed with SIGSEGV in imapx_parse_capability()
UpgradeStatus: Upgraded to wily on 2015-10-04 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Dave (swissbite) wrote :
Revision history for this message
Dave (swissbite) wrote :

After removing the imap accounts from ubuntu -> settings -> online accounts, evolution starts up and works with my exchange and google account. (Both defined in online accounts)

After trying to add an imap account on the online accounts, evolution was again unable to start up.
If I try to add the account within evolution, it will crash either at checking authentication credentials or after seting up account and test it.

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

 imapx_parse_capability (stream=stream@entry=0x7f59300056f0, cancellable=cancellable@entry=0x7f59a4042b90, error=error@entry=0x7f593fffea30) at camel-imapx-utils.c:515
 imapx_parse_status_capability (sinfo=0x7f59340057d0, error=0x7f593fffea30, cancellable=0x7f59a4042b90, stream=0x7f59300056f0) at camel-imapx-utils.c:2182
 imapx_parse_status (stream=0x7f59300056f0, mailbox=mailbox@entry=0x0, cancellable=cancellable@entry=0x7f59a4042b90, error=error@entry=0x7f593fffea30) at camel-imapx-utils.c:2452
 imapx_untagged_ok_no_bad (is=0x7f59ce97ef40, input_stream=0x7f59300056f0, cancellable=0x7f59a4042b90, error=0x7f593fffea30) at camel-imapx-server.c:2894
 imapx_untagged (is=is@entry=0x7f59ce97ef40, input_stream=input_stream@entry=0x7f59300056f0, cancellable=cancellable@entry=0x7f59a4042b90, error=error@entry=0x7f593fffea30) at camel-imapx-server.c:3085

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Dave (swissbite)
description: updated
Revision history for this message
Dave (swissbite) wrote :

Are there some news or what can I do to submit more informations?
Ist there a workaround?

information type: Private → Private Security
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Dave (swissbite) wrote :

The issue is still here. Do you have any further informations? Or ideas what I could to isolate the possible issues?

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.