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

[Steve Langasek]

The control center crashes whenever I try to select my webcam's mic as the default input in the sound tab.

This is a regression vs. last week in precise.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.2.2-2ubuntu10
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CheckboxSubmission: 017452a27eca3c8b498abbfa5ef91db9
CheckboxSystem: ecaaad6fa1e0799a0aa1126bf620f39e
Date: Wed Feb 15 10:33:42 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: gnome-control-center sound-nua
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f754d03ad80 <g_type_check_instance_cast+16>: mov (%rdi),%rax
 PC (0x7f754d03ad80) ok
 source "(%rdi)" (0x50ecf4e0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance_cast () 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/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to precise on 2011-11-08 (98 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src
usr_lib_gnome-control-center:
 deja-dup 21.2-0ubuntu4
 gnome-bluetooth 3.2.2-0ubuntu1
 indicator-datetime 0.3.1-0ubuntu5

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #932876, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.