[apport] gconf-editor crashed with SIGSEGV in g_hash_table_remove()

[David Baucum]

Binary package hint: gconf-editor

I was viewing the possible keymappings in apps->metacity and it crashed.

ProblemType: Crash
Architecture: i386
Date: Tue Mar 27 00:48:48 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gconf-editor
Package: gconf-editor 2.18.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gconf-editor
ProcCwd: /home/david
ProcEnviron:
 PATH=/home/david/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gconf-editor
StacktraceTop:
 g_hash_table_remove () from /usr/lib/libglib-2.0.so.0
 gconf_list_model_set_root_path ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux david-desktop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:IA__g_hash_table_remove (hash_table=0x1, key=0x815b1a0) at ghash.c:231
gconf_list_model_set_root_path (model=0x808d4a8, root_path=0x8318f08 "/apps/metacity/general") at gconf-list-model.c:128
gconf_editor_window_selection_changed (selection=0x8105420, window=0x80b1040) at gconf-editor-window.c:891
IA__g_cclosure_marshal_VOID__VOID (closure=0x815b500, return_value=0x0, n_param_values=1, param_values=0xbfdcbe9c, invocation_hint=0xbfdcbdac,
IA__g_closure_invoke (closure=0x815b500, return_value=0x0, n_param_values=1, param_values=0xbfdcbe9c, invocation_hint=0xbfdcbdac) at gclosure.c:490

[Sebastien Bacher (seb128)]

Thank you for your bug, the backtrace matches http://bugzilla.gnome.org/show_bug.cgi?id=362948 upstream

[Sebastien Bacher (seb128)]

Could you try if that's still happening on gutsy?

[David Baucum (maxolasersquad)]

This crash only happened once and is not reproducable.

[Robert Ancell (robert-ancell)]

Upstream reported this crash was replaced with a memory leak. Testing in Jaunty (gconf-editor 2.26.0) fails to reproduce the crash. Closing as the memory leak is a very minor issue and is tracked upstream. Please reopen if this crash reoccurs in Ubuntu.