gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value()

[Alex Mayorga]

Happened on restart after today's dist-upgrade on quantal.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gconf2 3.2.5-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
CheckboxSubmission: ed5dbdfb54bf5043a043813a33527c9f
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
Date: Mon Sep 3 12:13:01 2012
ExecutablePath: /usr/bin/gsettings-data-convert
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: gsettings-data-convert --file=/usr/lib/compiz/migration/compiz-profile-active-unity.convert
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gconf
StacktraceTop:
 g_settings_schema_get_value (schema=schema@entry=0x1de6200, key=key@entry=0x1ded5d0 "force-message-limit") at /build/buildd/glib2.0-2.33.10/./gio/gsettingsschema.c:640
 g_settings_schema_key_init (key=key@entry=0x7fff46d0fca0, schema=0x1de6200, name=name@entry=0x1ded5d0 "force-message-limit") at /build/buildd/glib2.0-2.33.10/./gio/gsettingsschema.c:751
 g_settings_set_value (settings=settings@entry=0x1dbaa30, key=key@entry=0x1ded5d0 "force-message-limit", value=0x1dd1720) at /build/buildd/glib2.0-2.33.10/./gio/gsettings.c:1350
 g_settings_set (settings=0x1dbaa30, key=0x1ded5d0 "force-message-limit", format=<optimized out>) at /build/buildd/glib2.0-2.33.10/./gio/gsettings.c:1449
 ?? ()
Title: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value()
UpgradeStatus: Upgraded to quantal on 2012-07-24 (41 days ago)
UserGroups: adm admin cdrom dialout dip lpadmin netdev plugdev sambashare vboxusers

[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 #945144, 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.