Ubuntu
gconf-editor package

when you run "gconf-editor %" it crashed with SIGABRT in raise()

Bug #761589 reported by confiq on 2011-04-15

This bug report is a duplicate of: Bug #755483: gconf-editor crashed with SIGABRT when given bad filename on cmdline. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gconf-editor (Ubuntu)	Confirmed	Low	Unassigned

Bug Description

Binary package hint: gconf-editor

The bad thing is "%" when you run it as parameter...
The importance of this issue should be low...

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gconf-editor 2.32.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 15 13:18:39 2011
ExecutablePath: /usr/bin/gconf-editor
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110409)
ProcCmdline: gconf-editor %
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: gconf-editor
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
Title: gconf-editor crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1185): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

See original description

Tags:

Revision history for this message

confiq (confiq) wrote on 2011-04-15:

CoreDump.gz Edit (665.6 KiB, application/x-gzip)
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (854 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (39.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (794 bytes, text/plain; charset="utf-8")
Registers.txt Edit (709 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (2.9 KiB, text/plain; charset="utf-8")

visibility:	private → public
description:	updated

Revision history for this message

Robert Roth (evfool) wrote on 2011-06-03:

I can confirm on i386, thus setting to confirmed and removing the amd64 tag.

Here's the GDB output:
Starting program: /usr/bin/gconf-editor %
[Thread debugging using libthread_db enabled]
[New Thread 0xb3f3fb70 (LWP 4168)]
[New Thread 0xb35ffb70 (LWP 4169)]
**
ERROR:gconf-tree-model.c:59:gconf_tree_model_get_tree_path_from_gconf_path: assertion failed: (key[0] == '/')

Program received signal SIGABRT, Aborted.
0xb7fe1424 in __kernel_vsyscall ()

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

tags:	removed: amd64
Changed in gconf-editor (Ubuntu):
status:	New → Confirmed
importance:	Undecided → Medium
importance:	Medium → Low

Revision history for this message

Robert Roth (evfool) wrote on 2011-06-03:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #755483, so it 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. Feel free to continue to report any other bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad