gsettings-data-convert crashed with SIGABRT in g_settings_set_value()

[Stefan Becker]

Binary package hint: gconf

after update 11.06 in oracle virtual box 4.04

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gconf2 2.32.1-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Mar 23 21:18:41 2011
ExecutablePath: /usr/bin/gsettings-data-convert
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110323)
ProcCmdline: gsettings-data-convert
ProcEnviron:
 LANGUAGE=C:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 6
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 SIGABRT in g_settings_set_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_settings_schema_get_value (schema=0x92fa400, key=0x933d528 "picture-uri") at /build/buildd/glib2.0-2.28.4/./gio/gsettingsschema.c:309
 g_settings_get_key_info (info=0xbfd467e0, settings=<value optimized out>, key=0x933d528 "picture-uri") at /build/buildd/glib2.0-2.28.4/./gio/gsettings.c:908
 g_settings_set_value (settings=0x92fa478, key=0x933d528 "picture-uri", value=0x9337e80) at /build/buildd/glib2.0-2.28.4/./gio/gsettings.c:1529
 g_settings_set (settings=0x92fa478, key=0x933d528 "picture-uri", format=0x804a510 "s") at /build/buildd/glib2.0-2.28.4/./gio/gsettings.c:1626
 handle_file (argc=1, argv=0xbfd46a54) at gsettings-data-convert.c:182

[Pedro Villavicencio (pedro)]

Thanks for the report, is this still an issue with latest packages?

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.