[color]: gnome-control-center crashed with SIGSEGV in gcm_prefs_device_changed_cb()

[James Tait]

This occurred just after I downloaded and imported a colour profile from System76. It seems to have imported the profile, but did not enable it - re-visiting the settings pane and enabling the profile succeeded.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu36
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Thu Sep 12 01:22:45 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-09-11 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130910)
MarkForUpload: True
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f38ae2acb95: mov 0x38(%rdx),%rdi
 PC (0x7f38ae2acb95) ok
 source "0x38(%rdx)" (0xaaaaaaaaaaaaaae2) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libcolor.so
 ?? () 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/libcolord.so.1
Title: [color]: gnome-control-center crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.20130903-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:
 gcm_prefs_device_changed_cb (device=0x7f389c00a780, prefs=0x26ef990) at cc-color-panel.c:1881
 _g_closure_invoke_va (closure=0x3fb3d10, return_value=0x0, instance=0x7f389c00a780, args=0x7fffba60d818, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.37.7/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x7f389c00a780, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffba60d818) at /build/buildd/glib2.0-2.37.7/./gobject/gsignal.c:3238
 g_signal_emit (instance=instance@entry=0x7f389c00a780, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.37.7/./gobject/gsignal.c:3386
 cd_device_dbus_signal_cb (proxy=<optimized out>, sender_name=<optimized out>, signal_name=0x4253d40 "Changed", parameters=<optimized out>, device=0x7f389c00a780) at cd-device.c:680

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[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