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 362948 - crash in Configuration Editor: Tried out different sett...
crash in Configuration Editor: Tried out different sett...
Status: RESOLVED DUPLICATE of bug 469173
Product: gconf-editor
Classification: Applications
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Gconf Editor Maintainers
Gconf Editor Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-17 19:45 UTC by Kjartan Maraas
Modified: 2008-01-01 18:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Kjartan Maraas 2006-10-17 19:45:36 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Tried out different settings under apps/compiz


Distribution: Fedora Core release 5.92 (FC6 Test3)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 78372864 vsize: 0 resident: 78372864 share: 0 rss: 12709888 rss_rlim: 0
CPU usage: start_time: 1161114147 rtime: 0 utime: 186 stime: 0 cutime:176 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

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 -1209120544 (LWP 3868)]
0x0029f402 in __kernel_vsyscall ()

+ Trace 76846

Thread 1 (Thread -1209120544 (LWP 3868))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #3 <signal handler called>
  • #4 IA__g_hash_table_remove
    at ghash.c line 231
  • #5 gconf_list_model_set_root_path
    at gconf-list-model.c line 128
  • #6 gconf_editor_window_selection_changed
    at gconf-editor-window.c line 887
  • #7 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #8 IA__g_closure_invoke
    at gclosure.c line 490
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #10 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #11 IA__g_signal_emit
    at gsignal.c line 2241
  • #12 _gtk_tree_selection_internal_select_node
    at gtktreeselection.c line 1409
  • #13 gtk_tree_view_real_set_cursor
    at gtktreeview.c line 12254
  • #14 gtk_tree_view_button_press
    at gtktreeview.c line 2610
  • #15 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #16 g_type_class_meta_marshal
    at gclosure.c line 567
  • #17 IA__g_closure_invoke
    at gclosure.c line 490
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #20 IA__g_signal_emit
    at gsignal.c line 2241
  • #21 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #22 IA__gtk_propagate_event
    at gtkmain.c line 2188
  • #23 IA__gtk_main_do_event
    at gtkmain.c line 1422
  • #24 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #25 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #26 g_main_context_iterate
    at gmain.c line 2677
  • #27 IA__g_main_loop_run
    at gmain.c line 2881
  • #28 IA__gtk_main
    at gtkmain.c line 1001
  • #29 main
    at main.c line 74
  • #30 __libc_start_main
    at libc-start.c line 231
  • #31 _start
  • #0 __kernel_vsyscall 






Comment 1


Kjartan Maraas





          2007-02-11 21:26:56 UTC
        



Can't reproduce this any more. Closing.






Comment 2


Sebastien Bacher





          2007-03-27 09:53:13 UTC
        



Ubuntu bug with a similar backtrace on GNOME 2.18: https://launchpad.net/bugs/96814






Comment 3


Kjartan Maraas





          2007-08-23 09:49:26 UTC
        



Could be related to bug 469173 I guess






Comment 4


Kjartan Maraas





          2007-08-27 12:50:06 UTC
        



I commited a fix for bug 469173 now. Could anyone test whether that fixes related bugs too? Released 2.18.2 with the fix.






Comment 5


Sebastien Bacher





          2007-08-29 21:02:25 UTC
        



the ubuntu bug submitter commented "This crash only happened once and is not reproducable."






Comment 6


Kjartan Maraas





          2008-01-01 18:32:11 UTC
        



Guess we can close this as a duplicate of the above.

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






Comment 7


Kjartan Maraas





          2008-01-01 18:32:44 UTC
        




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