Bug 411864 – crash in Configuration Editor: Trying to find the keywo...

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 411864 - crash in Configuration Editor: Trying to find the keywo...


Summary:	crash in Configuration Editor: Trying to find the keywo...


Status:	RESOLVED DUPLICATE of bug 373638

Product:	gconf-editor
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-25 11:43 UTC by emerg.reanimator
Modified:	2007-04-06 13:33 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description emerg.reanimator 2007-02-25 11:43:48 UTC

Version: 2.16.0

What were you doing when the application crashed?
Trying to find the keyword at root


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.2 2007-01-28 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 102973440 vsize: 102973440 resident: 15286272 share: 10375168 rss: 15286272 rss_rlim: -1
CPU usage: start_time: 1172403654 rtime: 72 utime: 66 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gconf-editor'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47806845848288 (LWP 8156)]
0x00002b7ae55e8ab5 in __libc_waitpid (pid=8157, stat_loc=0x7fffc974137c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 113741

Thread 1 (Thread 47806845848288 (LWP 8156))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 32
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 870
#2 <signal handler called>
#3 IA__g_enum_get_value
at genums.c line 365
#4 param_enum_validate
at gparamspecs.c line 443
#5 IA__g_param_value_validate
at gparam.c line 441
#6 g_object_constructor
at gobject.c line 684
#7 IA__g_object_newv
at gobject.c line 937
#8 IA__g_object_new_valist
at gobject.c line 1022
#9 IA__g_object_new
at gobject.c line 795
#10 IA__gtk_message_dialog_new
at gtkmessagedialog.c line 493
#11 gconf_search_dialog_search
at gconf-search-dialog.c line 55
#12 IA__g_closure_invoke
at gclosure.c line 490
#13 signal_emit_unlocked_R
at gsignal.c line 2440
#14 IA__g_signal_emit_valist
at gsignal.c line 2199
#15 IA__g_signal_emit
at gsignal.c line 2243
#16 gtk_button_key_release
at gtkbutton.c line 1414
#17 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#18 IA__g_closure_invoke
at gclosure.c line 490
#19 signal_emit_unlocked_R
at gsignal.c line 2478
#20 IA__g_signal_emit_valist
at gsignal.c line 2209
#21 IA__g_signal_emit
at gsignal.c line 2243
#22 gtk_widget_event_internal
at gtkwidget.c line 3911
#23 IA__gtk_propagate_event
at gtkmain.c line 2154
#24 IA__gtk_main_do_event
at gtkmain.c line 1422
#25 gdk_event_dispatch
at gdkevents-x11.c line 2320
#26 IA__g_main_context_dispatch
at gmain.c line 2045
#27 g_main_context_iterate
at gmain.c line 2677
#28 IA__g_main_loop_run
at gmain.c line 2881
#29 IA__gtk_main
at gtkmain.c line 1001
#30 main
at main.c line 74
#31 __libc_start_main
at libc-start.c line 238
#32 _start

0x00002b7ae55e8ab5	32	in ../sysdeps/unix/sysv/linux/waitpid.c
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]

Comment 1 Kjartan Maraas 2007-04-06 13:28:35 UTC

Same bug was closed as incomplete in bug 317985.

Comment 2 Kjartan Maraas 2007-04-06 13:33:27 UTC


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