gnome-control-center crashed with SIGSEGV

[shemgp]

I can't seem to unlock and edit users in the Users tab of the new gnome-control-center. It crashes with this crash.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Sep 15 21:47:25 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2015-09-28 (717 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9d7a218499: cmpq $0x0,0x58(%rax)
 PC (0x7f9d7a218499) ok
 source "$0x0" ok
 destination "0x58(%rax)" (0x00000058) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libnm.so.0
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-08-12 (33 days ago)
UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin lxd mail mythtv netdev plugdev sambashare sbuild scanner sudo video

[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 #1704618, 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.