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

Bug #960661 reported by Craig Chambers on 2012-03-20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)

Bug Description

Running Quick calibration with Huey. Calibration continued successfully.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Tue Mar 20 21:58:04 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gnome-control-center power
 Segfault happened at: 0x7f7f2a6e6a2d: mov 0x38(%rdx),%rdi
 PC (0x7f7f2a6e6a2d) 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
 ?? () from /usr/lib/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: Upgraded to precise on 2012-03-20 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
 activity-log-manager-control-center 0.9.3-0ubuntu1
 deja-dup 21.90-0ubuntu1
 gnome-bluetooth 3.2.2-0ubuntu3
 indicator-datetime 0.3.91-0ubuntu1

 gcm_prefs_device_changed_cb (device=0x7f7f3f3b8b40, prefs=0x7f7f3f3870a0) at cc-color-panel.c:1879
 _g_closure_invoke_va (closure=0x7f7f3f3a6900, return_value=0x0, instance=0x7f7f3f3b8b40, args=0x7fff7b558698, n_params=0, param_types=<optimized out>) at /build/buildd/glib2.0-2.31.22/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=0, var_args=<optimized out>) at /build/buildd/glib2.0-2.31.22/./gobject/gsignal.c:3207
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.31.22/./gobject/gsignal.c:3352
 ?? () from /tmp/tmp21aXp6/usr/lib/x86_64-linux-gnu/libcolord.so.1

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: [color]: gnome-control-center crashed with SIGSEGV in
- g_signal_emit_valist()
+ gcm_prefs_device_changed_cb()
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
information type: Private → Public
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

(there is a similar report on similar bug on https://bugzilla.redhat.com/show_bug.cgi?id=870661 which indicates the issue is not distro specific)

Sebastien Bacher (seb128) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Invalid
no longer affects: gnome-control-center
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.