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

[sam tygier]

Binary package hint: gconf

got this after running updates in maverick

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gconf2 2.31.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
Uname: Linux 2.6.35-8-generic x86_64
Architecture: amd64
Date: Tue Jul 20 23:56:30 2010
ExecutablePath: /usr/bin/gsettings-data-convert
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100605)
ProcCmdline: gsettings-data-convert
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gconf
StacktraceTop:
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist ()
 g_object_new () from /usr/lib/libgobject-2.0.so.0
Title: gsettings-data-convert crashed with signal 5 in g_object_newv()
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 g_settings_schema_new (
 g_settings_constructed (
 g_object_newv (object_type=<value optimized out>,
 g_object_new_valist (object_type=25429808,
 g_object_new (object_type=25429808,

[Pedro Villavicencio (pedro)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=625120

[YunQiang Su (wzssyqa)]

It seems disappeared these days.

[Pedro Villavicencio (pedro)]

does this happened again? can you reproduce it?

[sam tygier (samtygier)]

i have not seen it again (though apport does not show crashes after the release, so maybe it happens silently?). from upstream comment it looks like it would only show up during an upgrade, so maybe we would not expect to see twice on 1 machine.

[Eliah Kagan (degeneracypressure)]

This bug is still happening with Oneiric i386 (see duplicate bug 797712)--this happens every time I start a Lubuntu Desktop session on a Lubuntu Oneiric system. Also tagging powerpc (from duplicate bug 608486).

@sam tygier
You can manually (re)enable apport on a stable system. See https://wiki.ubuntu.com/Apport#How_to_enable_apport. If the issue is that a crash has occurred more than a certain number of times and therefore is not reported, you can fix that by moving the relevant .crash file out of /var/crash (or you can just delete the file, but sometimes it's useful to have a .crash file so you can perform operations on it, like retracing with apport-retrace).

[Shahar Or (mightyiam)]

Could this be still in precise?

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Beyond that, I have not seen a bug likes this in many years. If you could provide additional information on how it affects a currently supported release, that would be most helpful.