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

[tino227]

Gestern ein Ubuntu Upgrade von 13.04 auf 13.10 durchgeführt.

Heute habe ich mich mit einer GNOME Session angemeldet. Ich wollte die Neuerungen anschauen.

Via der Taskleiste hatte ich Bluetooth abgeschaltet. Anschliessend in den Einstellungen die 'Online-Konten' von 'Gnome' (leer) und dann von 'Unity' (mit Einträgen) geöffnet und auch wieder geschlossen. Dabei hatte ich nichts verstellt.

Kurz darauf kam diese Fehlermeldung ..

# lsb_release -rd
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gconf2 3.2.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Sun Aug 18 10:20:12 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gsettings-data-convert
InstallationDate: Installed on 2011-05-02 (838 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MarkForUpload: True
ProcCmdline: gsettings-data-convert --file=/usr/lib/compiz/migration/compiz-profile-active-unity.convert
Signal: 5
SourcePackage: gconf
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_set_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_set () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? ()
Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
UpgradeStatus: Upgraded to saucy on 2013-08-17 (0 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin 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.