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

[ofc587a87]

just after upgrading to 17.10:

Description: Ubuntu 17.10
Release: 17.10

gnome-control-center:
  Instalados: 1:3.26.1-0ubuntu4
  Candidato: 1:3.26.1-0ubuntu4
  Tabla de versión:
 *** 1:3.26.1-0ubuntu4 500
        500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 13:03:19 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-04-29 (174 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0x7f70af0a2d10 <g_settings_get_value+48>: cmp %rax,(%rdx)
 PC (0x7f70af0a2d10) ok
 source "%rax" ok
 destination "(%rdx)" (0x800000002) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_settings_get_value()
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin monetdb plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_settings_get_value (settings=0x558c04822d30, key=key@entry=0x558c01d483e9 "multi-monitor") at ../../../../gio/gsettings.c:1200
 g_settings_get_boolean (settings=<optimized out>, key=key@entry=0x558c01d483e9 "multi-monitor") at ../../../../gio/gsettings.c:2127
 ext_ubuntu_dock_placement_changed_callback (settings=<optimized out>, key=<optimized out>, user_data=<optimized out>) at cc-ubuntu-panel.c:251
 g_closure_invoke (closure=0x558c0484d1b0, return_value=0x0, n_param_values=2, param_values=0x7ffc5f37b700, invocation_hint=0x7ffc5f37b680) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x558c041ff720, detail=detail@entry=2747, instance=instance@entry=0x558c04ac0fa0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc5f37b700) at ../../../../gobject/gsignal.c:3635

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Sebastien Bacher (seb128)]

it's similar to bug #1725219

[Launchpad Janitor (janitor)]

[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]