unity-control-center crashed with SIGSEGV in _cogl_context_get_gl_extensions()

[Roderic Jones]

Fresh install. Nvidia Drivers and Chrome installed - nothing else. Unity control centre crashes.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Apr 13 14:42:50 2016
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2016-04-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412)
ProcCmdline: unity-control-center
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: unity-control-center
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_context_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
Title: unity-control-center crashed with SIGSEGV in cogl_context_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 _cogl_context_get_gl_extensions () from /tmp/apport_sandbox_V7ltZI/usr/lib/x86_64-linux-gnu/libcogl.so.20
 _cogl_driver_update_features () from /tmp/apport_sandbox_V7ltZI/usr/lib/x86_64-linux-gnu/libcogl.so.20
 _cogl_winsys_context_init () from /tmp/apport_sandbox_V7ltZI/usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_context_new () from /tmp/apport_sandbox_V7ltZI/usr/lib/x86_64-linux-gnu/libcogl.so.20

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.