gnome-control-center crashed with SIGSEGV

[Rocko]

g-c-c segfaults every time I enter my admin user password to try to unlock the 'Users' section.

ie

1. Run g-c-c
2. Search for 'Users' and click on the 'Users' section that appears on the left hand side
3. Wait for several sections until the Users pane appears
3. Click on the 'Unlock' button and enter the (correct) password in the 'Authentication Required' window that appears.
4. Press Authenticate.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.25.92.1-0ubuntu1
Uname: Linux 4.13.1-041301-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 11 13:51:38 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-08-16 (25 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcCmdline: gnome-control-center
SegvAnalysis:
 Segfault happened at: 0x7f68ac0b5499: cmpq $0x0,0x58(%rax)
 PC (0x7f68ac0b5499) 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-17 (25 days ago)
UserGroups:

[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.