gnome-control-center crashed with SIGSEGV in __GI_____strtoul_l_internal()

[Dennis Mungai Lin.Jr.]

Trying to access the audio settings panel triggers this error.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-control-center 1:3.18.2-1ubuntu6
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 27 14:15:13 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-07-25 (125 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0x7fe2ddf1d924 <__GI_____strtoul_l_internal+68>: movsbq (%r14),%rax
 PC (0x7fe2ddf1d924) ok
 source "(%r14)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 __GI_____strtoul_l_internal (nptr=0x0, endptr=0x7ffcf5eb89a8, base=10, group=<optimized out>, loc=0x7fe2de2a4b60 <_nl_C_locobj>) at ../stdlib/strtol_l.c:293
 ?? () 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
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
Title: gnome-control-center crashed with SIGSEGV in __GI_____strtoul_l_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd 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 #1712961, 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.