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 80768 - panel crashed while opening Gconf editor
panel crashed while opening Gconf editor
Status: RESOLVED DUPLICATE of bug 78372
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-04 07:22 UTC by Thilo
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Thilo 2002-05-04 07:21:37 UTC 
Package: gnome-panel
Severity: major
Version: 1.5.19
Synopsis: panel crashed while opening Gconf editor
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (1.116.1)

Description:
Description of Problem:

Panel crashed

Steps to reproduce the problem:
1.  Opened Gconf editor


Actual Results:

panel crashed






Debugging Information:

Backtrace was generated from '/home/vinci/garnome/bin/gnome-panel'

[New Thread 1024 (LWP 8557)]
0x40902a39 in wait4 () from /lib/libc.so.6

+ Trace 21701

Thread 1 (Thread 1024 (LWP 8557))

  • #0 wait4
    from /lib/libc.so.6
  • #1 __check_rhosts_file
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 593
  • #4 pthread_sighandler
    from /lib/libpthread.so.0
  • #5 sigaction
    from /lib/libc.so.6
  • #6 gtk_object_dispose
    at gtkobject.c line 375
  • #7 gtk_widget_dispose
    at gtkwidget.c line 5599
  • #8 g_object_run_dispose
    at gobject.c line 469
  • #9 gtk_object_destroy
    at gtkobject.c line 358
  • #10 gtk_widget_destroy
    at gtkwidget.c line 1581
  • #11 set_das_pixmap
    at foobar-widget.c line 514
  • #12 active_window_changed
    at foobar-widget.c line 593
  • #13 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #14 g_closure_invoke
    at gclosure.c line 437
  • #15 signal_emit_unlocked_R
    at gsignal.c line 2341
  • #16 g_signal_emit_valist
    at gsignal.c line 2100
  • #17 g_signal_emit
    at gsignal.c line 2144
  • #18 emit_active_window_changed
    at screen.c line 1149
  • #19 update_active_window
    at screen.c line 1033
  • #20 do_update_now
    at screen.c line 1107
  • #21 update_idle
    at screen.c line 1122
  • #22 g_idle_dispatch
    at gmain.c line 3129
  • #23 g_main_dispatch
    at gmain.c line 1617
  • #24 g_main_context_dispatch
    at gmain.c line 2161
  • #25 g_main_context_iterate
    at gmain.c line 2242
  • #26 g_main_loop_run
    at gmain.c line 2462
  • #27 gtk_main
    at gtkmain.c line 912
  • #28 main
    at main.c line 233
  • #0 wait4
    from /lib/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-04 03:21 -------

Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Comment 1 Heath Harrelson 2002-05-07 15:56:35 UTC 
This looks like a duplicate of bug 78372.  The problem there was
corruption of GConf info for the panel, and it was solved by running
gconftool-2 --shutdown; rm -rf ~/.gconf/apps/panel to clear the panel
setup.

Please give that a try, and feel free to reopen this bug if that
doesn't fix the problem.

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