Just installed BETA update, restarted to apply, and got error message on first boot. gsettings-data-convert crashed with signal 5 in g_settings_set_value()

[Don Daniels]

Upgraded from 12.04 to 12.10 BETA. After install, it asked to restart to activate changes. Hung on blank purple screen for a long time, then gave an error message that didn't last long enough for me to read, then seemed to finish booting at least with partial capabilities. LaunchPad popped up with this form to report the bug. Wanted to send with the information IT captured, will now try reboot, check for updates that occured overnight, and see if it happens again.

Toshiba Satellite M45 -S359 with Dual Boot (Win XP)

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gconf2 3.2.5-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Mon Sep 10 02:04:21 2012
ExecutablePath: /usr/bin/gsettings-data-convert
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
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:
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 g_settings_set_value () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 g_settings_set () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? ()
Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
UpgradeStatus: Upgraded to quantal on 2012-09-10 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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