gconf-cleaner crashed with SIGABRT in raise()

[SiRiusCb]

Crash when try to make a backup before to proceed in cleaning

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gconf-cleaner 0.0.3-5 [modified: usr/bin/gconf-cleaner]
Uname: Linux 3.3.0-030300-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Tue Mar 27 11:16:44 2012
ExecutablePath: /usr/bin/gconf-cleaner
ProcCmdline: gconf-cleaner
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gconf-cleaner
Title: gconf-cleaner crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_assertion_message_cmpstr (domain=0x4248eff4 "x\356HB\226\256:B", file=0x4226c7c5 "\201\303;L\003", line=1112076276, func=0x8772c60 "\200\344-B\200\344-Balue>\n", expr=0x4248eff4 "x\356HB\226\256:B", arg1=0x86c7000 "\230Ev\b\016", cmp=0x8767500 " ", arg2=0x6aa8cd00 <Address 0x6aa8cd00 out of bounds>) at /build/buildd/glib2.0-2.32.0/./glib/gtestutils.c:1910
 ?? ()
 ?? () from /tmp/tmpf_CplX/lib/i386-linux-gnu/libglib-2.0.so.0

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libglib2.0-0 version 2.31.22-0ubuntu1 required, but 2.32.0-0ubuntu1 is available
libatk1.0-0 version 2.3.95-0ubuntu1 required, but 2.4.0-0ubuntu1 is available
outdated debug symbol package for libatk1.0-0: package version 2.4.0-0ubuntu1 dbgsym version 2.3.95-0ubuntu1
libatk1.0-data version 2.3.95-0ubuntu1 required, but 2.4.0-0ubuntu1 is available
outdated debug symbol package for libgconf2-4: package version 3.2.5-0ubuntu2 dbgsym version 3.2.3-0ubuntu0.1
outdated debug symbol package for librsvg2-common: package version 2.36.0-0ubuntu1 dbgsym version 2.35.2-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!