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 123950 - crash when gconf directory are removed
crash when gconf directory are removed
Status: RESOLVED DUPLICATE of bug 124662
Product: gconf-editor
Classification: Applications
Component: general
2.4.x
Other Linux
: Normal critical
: ---
Assigned To: Gconf Editor Maintainers
Gconf Editor Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-10-06 13:03 UTC by Frederic Crozat
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Frederic Crozat 2003-10-06 13:03:14 UTC 
to reproduce :
1/open gconf-editor and display a deep directory with it (for instance
/apps/panel/profiles/default/applets/whatever

2/in a terminal, run gconftool --recursive-unset
/apps/panel/profiles/default/applets/whatever

-first (little) bug, gconf-editor should have monitor this node removal
(all gconf key are gone but not the node)
-more serious : close parent node two level up and open them again => crash.
Comment 1 Fernando Herrera 2004-01-15 17:43:17 UTC 
Frederic, can you attach a stack trace? I think this is a dupplicate
of 124662 or 128272
Comment 2 Frederic Crozat 2004-01-16 10:04:51 UTC 
Backtrace obtained with HEAD from today :

Program received signal SIGSEGV, Segmentation fault.

+ Trace 43273

Thread 16384 (LWP 19202)

  • #0 gconf_tree_model_ref_node
    at gconf-tree-model.c line 419
  • #1 gtk_tree_model_ref_node
    at gtktreemodel.c line 1207
  • #2 gtk_tree_model_sort_ref_node
    at gtktreemodelsort.c line 1231
  • #3 gtk_tree_model_ref_node
    at gtktreemodel.c line 1207
  • #4 gtk_tree_view_build_tree
    at gtktreeview.c line 7075
  • #5 gtk_tree_view_real_expand_row
    at gtktreeview.c line 9880
  • #6 gtk_tree_view_button_release
    at gtktreeview.c line 2483
  • #7 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #8 g_type_class_meta_marshal
    at gclosure.c line 514
  • #9 g_closure_invoke
    at gclosure.c line 437
  • #10 signal_emit_unlocked_R
    at gsignal.c line 2474
  • #11 g_signal_emit_valist
    at gsignal.c line 2205
  • #12 g_signal_emit
    at gsignal.c line 2239
  • #13 gtk_widget_event_internal
    at gtkwidget.c line 3542
  • #14 gtk_propagate_event
    at gtkmain.c line 2330
  • #15 gtk_main_do_event
    at gtkmain.c line 1579
  • #16 gdk_event_dispatch
    at gdkevents-x11.c line 2111
  • #17 g_main_dispatch
    at gmain.c line 1752
  • #18 g_main_context_dispatch
    at gmain.c line 2300
  • #19 g_main_context_iterate
    at gmain.c line 2381
  • #20 g_main_loop_run
    at gmain.c line 2601
  • #21 gtk_main
    at gtkmain.c line 1169
  • #22 main
    at main.c line 94
  • #23 __libc_start_main
    from /lib/i686/libc.so.6 






Comment 3


Fernando Herrera





          2004-01-21 07:47:07 UTC
        



Yep, it's the same bug.

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