gconfd-2 crashed with SIGABRT in g_assertion_message()

Bug #883384 reported by Dmitry Shachnev
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
New
Undecided
Unassigned

Bug Description

Possibly the same as bug 882678.

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 i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Sat Oct 29 10:09:48 2011
ExecutablePath: /usr/lib/libgconf2-4/gconfd-2
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: /usr/lib/libgconf2-4/gconfd-2
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=ru_RU.UTF-8
 PATH=(custom, no user)
 LANGUAGE=ru:en
 LANG=ru_RU.UTF-8
Signal: 6
SourcePackage: gconf
StacktraceTop:
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 gconf_database_set_sources ()
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gconfd-2 crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (56 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev nopasswdlogin plugdev sambashare tape video

visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-i386-retrace
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.