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

[David Gardner]

Just trying to start control center crashed.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 9 21:56:40 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-10-03 (7 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0c9fb850f5 <__GI_____strtoul_l_internal+53>: movsbq (%r14),%rax
 PC (0x7f0c9fb850f5) 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=0x7ffe352c29a8, base=10, group=<optimized out>, loc=0x7f0c9ff20800 <_nl_C_locobj>) at ../stdlib/strtol_l.c:292
 ?? () 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: Upgraded to artful on 2017-10-03 (6 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 #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.