evolution crashed with SIGSEGV

[Steven Wolf]

$ lsb_release -rd
Description: Ubuntu 15.10
Release: 15.10

$ apt-cache policy evolution
evolution:
  Installed: 3.16.5-1ubuntu3.1
  Candidate: 3.16.5-1ubuntu3.1
  Version table:
 *** 3.16.5-1ubuntu3.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     3.16.5-1ubuntu3 0
        500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

I expected an email message to open, instead of opening, evolution crashed.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: evolution 3.16.5-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Jan 4 15:01:26 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2015-10-28 (68 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: evolution
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8801bd37f4: mov 0x8(%rcx),%r10
 PC (0x7f8801bd37f4) ok
 source "0x8(%rcx)" (0xbadbeef7ffededf5) not located in a known VMA region (needed readable region)!
 destination "%r10" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
Title: evolution crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #1514855, 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.