dconf-service crashed with signal 5 in g_warn_message()

Bug #868651 reported by xtracool_protik
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
d-conf (Ubuntu)
New
Medium
Unassigned

Bug Description

I don't exactly know how to reproduce this one

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: dconf-gsettings-backend 0.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 27 22:07:21 2011
ExecutablePath: /usr/lib/d-conf/dconf-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/d-conf/dconf-service
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 5
SourcePackage: d-conf
StacktraceTop:
 g_warn_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? ()
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
Title: dconf-service crashed with signal 5 in g_warn_message()
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (9 days ago)
UserGroups:

Revision history for this message
xtracool_protik (protik-seeker) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_warn_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=<optimized out>, warnexpr=0x7fb2934f5740 "\r") at /build/buildd/glib2.0-2.30.0/./glib/gmessages.c:626
 ?? () from /tmp/tmpInnCmy/lib64/ld-linux-x86-64.so.2
 dconf_state_init_session (state=<optimized out>) at dconf-state.c:49
 dconf_state_init (state=0x7fffe39a3f40) at dconf-state.c:76
 main () at service.c:441

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 d-conf (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
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.