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

[Víctor Adrián de la Cruz Serrano]

lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10

apt-cache policy gnome-control-center
gnome-control-center:
  Instalados: 1:3.1.91-0ubuntu4
  Candidato: 1:3.1.91-0ubuntu4
  Tabla de versión:
 *** 1:3.1.91-0ubuntu4 0
        500 http://mx.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.91-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
Date: Thu Sep 8 12:56:49 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: gnome-control-center display
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=es_MX:es
 LANG=es_MX.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f34fa1956cc: mov (%rax),%rdi
 PC (0x7f34fa1956cc) ok
 source "(%rax)" (0xaaaaaaaaaaaaaaaa) 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/control-center-1/panels/libdisplay.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () 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
Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Víctor Adrián de la Cruz Serrano (adriandcs)]

I was changing my dual screen configuration setup before crash.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #843274, 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.