gnome-control-center crashed with SIGSEGV

[John Clemens]

I was playing around with gnome calendar adding my google accounts (and thus my google personal and shared family calendars). Then the crash dialog popped up, once after I added both accounts. It does look like it added at least one calendar correctly for each account (but not the others).

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 6 23:30:02 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2015-08-19 (780 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150818)
ProcCmdline: /usr/bin/gnome-control-center
ProcEnviron:
 LD_LIBRARY_PATH=<set>
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f2f08e6eb3b: mov 0x8(%rax),%rax
 PC (0x7f2f08e6eb3b) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
Title: gnome-control-center crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-01 (5 days ago)
UserGroups: adm cdrom dip 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 #1712085, 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.