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

[Barry Fishman]

Failed when I was changing security to shut off logging

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu40
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Mon Sep 30 17:44:32 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-09-29 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MarkForUpload: True
ProcCmdline: gnome-control-center
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f07cccd45b9 <g_type_check_instance+25>: mov (%rax),%rdi
 PC (0x7f07cccd45b9) ok
 source "(%rax)" (0x300000007400) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm barry cdrom dip lpadmin plugdev sambashare staff sudo users util
usr_lib_gnome-control-center:
 activity-log-manager 0.9.7-0ubuntu4
 deja-dup 27.3.1-0ubuntu1
 gnome-control-center-datetime 13.10.0+13.10.20130930-0ubuntu1
 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
 gnome-control-center-unity 1.3daily13.06.14.1-0ubuntu1

[Apport retracing service (apport)]

StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0xe89c80) at /build/buildd/glib2.0-2.38.0/./gobject/gtype.c:4082
 g_signal_emit_valist (instance=0xe89c80, signal_id=378, detail=0, var_args=var_args@entry=0x7fff2e33e778) at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c:3109
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c:3386
 emit_manager_changed (data=<optimized out>) at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkrecentmanager.c:1387
 gdk_threads_dispatch (data=0xda1c80, data@entry=<error reading variable: value has been optimized out>) at /build/buildd/gtk+3.0-3.8.4/./gdk/gdk.c:788

[Sebastien Bacher (seb128)]

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions