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

[berloga.bob]

in tab "monitors" show error "Расширение RANDR отсутствует"

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.92-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Sun Mar 25 21:42:25 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120217)
ProcCmdline: gnome-control-center display
ProcEnviron:
 SHELL=/bin/bash
 LANG=ru_RU.UTF-8
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
Title: gnome-control-center crashed with SIGSEGV in gtk_widget_size_allocate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 gtk_widget_size_allocate (widget=0x0, allocation=0xbf976150) at /build/buildd/gtk+3.0-3.3.20/./gtk/gtkwidget.c:4872
 cc_panel_size_allocate (widget=0xb925f030, allocation=0xbf9764bc) at cc-panel.c:180
 g_cclosure_marshal_VOID__BOXEDv (closure=0xb905f110, return_value=0x0, instance=0xb925f030, args=0xbf97644c "\274d\227\277\340d\227\277\350d\227\277\210\221\030\271\243\026T\267", marshal_data=0xb77411e0, n_params=1, param_types=0xb905f150) at /build/buildd/glib2.0-2.31.22/./gobject/gmarshal.c:1160
 g_type_class_meta_marshalv (closure=0xb905f110, return_value=0x0, instance=0xb925f030, args=0xbf97644c "\274d\227\277\340d\227\277\350d\227\277\210\221\030\271\243\026T\267", marshal_data=0x6c, n_params=1, param_types=0xb905f150) at /build/buildd/glib2.0-2.31.22/./gobject/gclosure.c:997
 _g_closure_invoke_va (closure=0xb905f110, return_value=0x0, instance=0xb925f030, args=0xbf97644c "\274d\227\277\340d\227\277\350d\227\277\210\221\030\271\243\026T\267", n_params=1, param_types=0xb905f150) at /build/buildd/glib2.0-2.31.22/./gobject/gclosure.c:840

[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