Bug 334580 – gconf-editor crashed

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 334580 - gconf-editor crashed


Summary:	gconf-editor crashed


Status:	RESOLVED DUPLICATE of bug 332931

Product:	gconf-editor
Classification:	Applications
Component:	general
Version:	2.14.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Gconf Editor Maintainers
QA Contact:	Gconf Editor Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-03-14 22:08 UTC by Wouter Bolsterlee (uws)
Modified:	2006-03-15 18:59 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Wouter Bolsterlee (uws) 2006-03-14 22:08:21 UTC

Steps to reproduce (over here, at least):
1. Start gconf-editor
2. Open the search dialog
3. Type "numlock"
4. Check the first checkbox (search in key names)
5. Find
6. Select the found peripherals/host-foo/... numlock setting
7. Toggle the checkbox
8. Boom!

This is with a fresh compiled version from CVS HEAD, which presents itself as 2.14.0, hence the version of this bug report.

Backtrace below:

$ gdb gconf-editor
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run
Starting program: /opt/gnome-2-14/bin/gconf-editor
[Thread debugging using libthread_db enabled]
[New Thread -1225434624 (LWP 9848)]
*** glibc detected *** free(): invalid pointer: 0x08486c40 ***

Program received signal SIGABRT, Aborted.

+ Trace 66938

Thread NaN (LWP 9848)

#0 raise
from /lib/tls/libc.so.6
#1 abort
from /lib/tls/libc.so.6
#2 __fsetlocking
from /lib/tls/libc.so.6
#3 malloc_usable_size
from /lib/tls/libc.so.6
#4 free
from /lib/tls/libc.so.6
#5 IA__g_free
at gmem.c line 187
#6 gconf_editor_gconf_value_changed
at gconf-editor-window.c line 953
#7 IA__g_closure_invoke
at gclosure.c line 490
#8 signal_emit_unlocked_R
at gsignal.c line 2438
#9 IA__g_signal_emit_valist
at gsignal.c line 2197
#10 IA__g_signal_emit
at gsignal.c line 2241
#11 gconf_cell_renderer_activate
at gconf-cell-renderer.c line 320
#12 IA__gtk_cell_renderer_activate
at gtkcellrenderer.c line 634
#13 gtk_tree_view_column_cell_process_action
at gtktreeviewcolumn.c line 2869
#14 _gtk_tree_view_column_cell_event
at gtktreeviewcolumn.c line 3143
#15 gtk_tree_view_button_press
at gtktreeview.c line 2368
#16 _gtk_marshal_BOOLEAN__BOXED
#17 g_type_class_meta_marshal
at gclosure.c line 567
#18 IA__g_closure_invoke
at gclosure.c line 490
#19 signal_emit_unlocked_R
at gsignal.c line 2476
#20 IA__g_signal_emit_valist
at gsignal.c line 2207
#21 IA__g_signal_emit
at gsignal.c line 2241
#22 gtk_widget_event_internal
at gtkwidget.c line 3732
#23 IA__gtk_propagate_event
at gtkmain.c line 2175
#24 IA__gtk_main_do_event
at gtkmain.c line 1412
#25 gdk_event_dispatch
at gdkevents-x11.c line 2291
#26 IA__g_main_context_dispatch
at gmain.c line 1916
#27 g_main_context_iterate
at gmain.c line 2547
#28 IA__g_main_loop_run
at gmain.c line 2751
#29 IA__gtk_main
at gtkmain.c line 991
#30 main
at main.c line 93

Comment 1 Sergej Kotliar 2006-03-15 18:59:36 UTC


*** This bug has been marked as a duplicate of 332931 ***