gnome-control-center crashed with SIGABRT in gcm_prefs_profile_remove_cb()

[Evan Huus]

Was playing around with Colour Management, and somehow the "Remove Profile" button ended up active even though no profile was selected. Clicking the button resulted in this crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.91-0ubuntu8
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Sun Sep 18 12:16:04 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/control-center-1/panels/libcolor.so
Title: gnome-control-center crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to oneiric on 2011-08-12 (36 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 deja-dup 19.92-0ubuntu1
 empathy 3.1.91-0ubuntu2
 gnome-bluetooth 3.1.4-0ubuntu2
 indicator-datetime 0.2.95-0ubuntu1

[Apport retracing service (apport)]

StacktraceTop:
 g_assertion_message (domain=0x21864e30 "color-cc-panel", file=0x21865203 "cc-color-panel.c", line=479, func=0x218655bd "gcm_prefs_profile_remove_cb", message=<optimized out>) at /build/buildd/glib2.0-2.29.90/./glib/gtestutils.c:1425
 gcm_prefs_profile_remove_cb (widget=<optimized out>, prefs=0x22accb58) at cc-color-panel.c:479
 g_cclosure_marshal_VOID__VOID (closure=0x22ccc520, return_value=0x0, n_param_values=1, param_values=0x22cd2f18, invocation_hint=0xbfcc0380, marshal_data=0x0) at /build/buildd/glib2.0-2.29.90/./gobject/gmarshal.c:85
 g_closure_invoke (closure=0x22ccc520, return_value=0x0, n_param_values=1, param_values=0x22cd2f18, invocation_hint=0xbfcc0380) at /build/buildd/glib2.0-2.29.90/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=0x22ce8f58, detail=0, instance=0x22cf59b0, emission_return=0x0, instance_and_params=0x22cd2f18) at /build/buildd/glib2.0-2.29.90/./gobject/gsignal.c:3272

[Sebastien Bacher (seb128)]

Thank you for your bug report, could you try if that's still an issue on current oneiric with GNOME 3.2?

[Evan Huus (eapache)]

Still partially an issue. I am able to get the "Remove Profile" button active even though no profile is selected, however pressing it now seems safe. Somebody added a NULL check somewhere without fixing the root cause :)

Steps to reproduce:
1. Open the Color applet and select a device.
2. Click "Add Profile" and then "Add" (it doesn't matter which profile you add). The new profile should be the one whose radio button is selected.
3. Click on the new, selected profile and click "Remove Profile"

The original, default profile should now have its radio button selected, but the element itself does not have focus. The "Remove Profile" button is still clickable, even though none of the profiles have focus.

Importance should be Minor, as this has gone from a crasher to a minor UI inconsistency.

[Pedro Villavicencio (pedro)]

a new report should be opened with that then, closing this one as closed, thanks.

[Evan Huus (eapache)]

New bug opened as per request: bug #869603.