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

[Felix Möller]

This seems similar to bug #817460 however, that one is quiet old. So maybe this is a new one. Let's see the trace.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gconf2 3.2.5-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.5.1-0ubuntu1
Architecture: amd64
Date: Thu Aug 23 21:57:58 2012
ExecutablePath: /usr/bin/gsettings-data-convert
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331)
ProcCmdline: gsettings-data-convert --file=/usr/lib/compiz/migration/compiz-profile-active-unity.convert
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gconf
StacktraceTop:
 g_settings_schema_get_value (schema=schema@entry=0x1e92440, key=key@entry=0x1e98d20 "alt-tab-bias_viewport") at /build/buildd/glib2.0-2.33.10/./gio/gsettingsschema.c:640
 g_settings_schema_key_init (key=key@entry=0x7fff092aeef0, schema=0x1e92440, name=name@entry=0x1e98d20 "alt-tab-bias_viewport") at /build/buildd/glib2.0-2.33.10/./gio/gsettingsschema.c:751
 g_settings_set_value (settings=settings@entry=0x1e845e0, key=key@entry=0x1e98d20 "alt-tab-bias_viewport", value=0x1e998a0) at /build/buildd/glib2.0-2.33.10/./gio/gsettings.c:1350
 g_settings_set (settings=0x1e845e0, key=0x1e98d20 "alt-tab-bias_viewport", 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-08-02 (20 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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.