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

[bengy]

se cerro inesperadamente

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Apr 12 22:44:42 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: gnome-control-center --overview
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 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
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
Title: gnome-control-center crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-04-12 (1 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare video
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu1

[Apport retracing service (apport)]

StacktraceTop: __GI___open_catalog (cat_name=Cannot access memory at address 0x175dd7

[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