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

Bug #713000 reported by Xavier Fung
76
This bug affects 17 people
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gconf

Apport comes up after a restart with this error.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gconf2 2.32.1-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 4 18:46:02 2011
ExecutablePath: /usr/bin/gsettings-data-convert
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: gsettings-data-convert
ProcEnviron:
 LANGUAGE=en_HK:en
 LANG=en_HK.UTF-8
 LC_MESSAGES=en_HK.utf8
 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_settings_set_value () from /usr/lib/libgio-2.0.so.0
 g_settings_set () from /usr/lib/libgio-2.0.so.0
 ?? ()
Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Xavier Fung (xavier114fch) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gconf (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libdrm-radeon1: installed version 2.4.23+git20110128.550fe2ca-0ubuntu0sarvatt3, latest version: 2.4.23-1ubuntu3
libxcb1: installed version 1.7-0ubuntu0sarvatt2, latest version: 1.6-1
libx11-data: installed version 2:1.3.4+git20100720.554da76e-0ubuntu0sarvatt3, latest version: 2:1.3.3-3ubuntu3
libdrm2-dbg: installed version 2.4.23+git20110128.550fe2ca-0ubuntu0sarvatt3, latest version: 2.4.23-1ubuntu3
libdrm-intel1-dbg: installed version 2.4.23+git20110128.550fe2ca-0ubuntu0sarvatt3, latest version: 2.4.23-1ubuntu3
libdrm-nouveau1a-dbg: installed version 2.4.23+git20110128.550fe2ca-0ubuntu0sarvatt3, latest version: 2.4.23-1ubuntu3
libsqlite3-0: installed version 3.7.4-2ubuntu1, latest version: 3.7.4-2ubuntu2
libdrm-intel1: installed version 2.4.23+git20110128.550fe2ca-0ubuntu0sarvatt3, latest version: 2.4.23-1ubuntu3
libxcb1-dbg: installed version 1.7-0ubuntu0sarvatt2, latest version: 1.6-1
libsqlite3-0-dbg: installed version 3.7.4-2ubuntu1, latest version: 3.7.4-2ubuntu2
libdrm-radeon1-dbg: installed version 2.4.23+git20110128.550fe2ca-0ubuntu0sarvatt3, latest version: 2.4.23-1ubuntu3
libdrm-nouveau1a: installed version 2.4.23+git20110128.550fe2ca-0ubuntu0sarvatt3, latest version: 2.4.23-1ubuntu3
libx11-6: installed version 2:1.3.4+git20100720.554da76e-0ubuntu0sarvatt3, latest version: 2:1.3.3-3ubuntu3
libdrm2: installed version 2.4.23+git20110128.550fe2ca-0ubuntu0sarvatt3, latest version: 2.4.23-1ubuntu3
libx11-6-dbg: installed version 2:1.3.4+git20100720.554da76e-0ubuntu0sarvatt3, latest version: 2:1.3.3-3ubuntu3

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
tommy (mesilliac) wrote :

I ecountered this after upgrading fully using a different account on the same computer.

As soon as I logged in as another user, I encountered this problem.

I haven't noticed any detrimental effects, but if there is any more info I can provide I would be happy to.

I logged into yet another user account (I keep multiple accounts for testing purposes), and did NOT encounter the problem again, so, beats me what it was about.

I am aware this is a very old report, will file a new one if any new info turns up. Currently running quantal (development version).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.