gconfd-2 crashed with SIGABRT in g_assertion_message()

Bug #883230 reported by Cristian Aravena Romero on 2011-10-28
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
Undecided
Unassigned

Bug Description

Upgrade system and crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libgconf2-4 3.2.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Fri Oct 28 16:04:14 2011
ExecutablePath: /usr/lib/libgconf2-4/gconfd-2
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: /usr/lib/libgconf2-4/gconfd-2
Signal: 6
SourcePackage: gconf
StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x408300 "gconf_database_set_sources", message=0x7f9239fd5717 "code should not be reached") at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1425
 gconf_database_set_sources ()
 ?? ()
 g_timeout_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3907
 g_main_dispatch (context=0x92e130) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:2441
Title: gconfd-2 crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to oneiric on 2011-10-04 (24 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #882525, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments