Bug 95696 – GNOME panel had an error and then closed.

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 95696 - GNOME panel had an error and then closed.


Summary:	GNOME panel had an error and then closed.


Status:	RESOLVED DUPLICATE of bug 77540

Product:	gnome-panel
Classification:	Other
Component:	panel
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-10-14 03:46 UTC by s6260047
Modified:	2004-12-22 21:47 UTC

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

Description s6260047 2002-10-14 03:46:25 UTC

Package: gnome-panel
Severity: normal
Version: 1.4.0.4
Synopsis: GNOME panel had an error and then closed.
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel

Description:
i login and get started in GNOME.

then the program "panel" had an error and the closed.

i dont know why.

i just installed red hat 7.3 two days ago.

thx for help


Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x420b4769 in wait4 () from /lib/i686/libc.so.6

+ Trace 28766

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 gnome_segv_handle
from /usr/lib/libgnomeui.so.32
#3 <signal handler called>
#4 chunk_alloc
from /lib/i686/libc.so.6
#5 calloc
from /lib/i686/libc.so.6
#6 g_malloc0
from /usr/lib/libglib-1.2.so.0
#7 gdk_pixmap_new
from /usr/lib/libgdk-1.2.so.0
#8 panel_widget_draw_all
#9 panel_widget_size_allocate
#10 gtk_marshal_NONE__POINTER
from /usr/lib/libgtk-1.2.so.0
#11 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#12 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#13 gtk_widget_size_allocate
from /usr/lib/libgtk-1.2.so.0
#14 gtk_frame_size_allocate
from /usr/lib/libgtk-1.2.so.0
#15 gtk_marshal_NONE__POINTER
from /usr/lib/libgtk-1.2.so.0
#16 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#17 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#18 gtk_widget_size_allocate
from /usr/lib/libgtk-1.2.so.0
#19 gtk_container_resize_children
from /usr/lib/libgtk-1.2.so.0
#20 gtk_window_move_resize
from /usr/lib/libgtk-1.2.so.0
#21 gtk_window_check_resize
from /usr/lib/libgtk-1.2.so.0
#22 gtk_marshal_NONE__NONE
from /usr/lib/libgtk-1.2.so.0
#23 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#24 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#25 gtk_container_check_resize
from /usr/lib/libgtk-1.2.so.0
#26 gtk_container_idle_sizer
from /usr/lib/libgtk-1.2.so.0
#27 g_idle_dispatch
from /usr/lib/libglib-1.2.so.0
#28 g_main_dispatch
from /usr/lib/libglib-1.2.so.0
#29 g_main_iterate
from /usr/lib/libglib-1.2.so.0
#30 g_main_run
from /usr/lib/libglib-1.2.so.0
#31 gtk_main
from /usr/lib/libgtk-1.2.so.0
#32 main
#33 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 gnome_segv_handle
from /usr/lib/libgnomeui.so.32
#3 <signal handler called>
#4 chunk_alloc
from /lib/i686/libc.so.6
#5 calloc
from /lib/i686/libc.so.6
#6 g_malloc0
from /usr/lib/libglib-1.2.so.0
#7 gdk_pixmap_new
from /usr/lib/libgdk-1.2.so.0





------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-13 23:46 -------

The original reporter (s6260047@nutu.edu.tw) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.

Comment 1 Vincent Untz 2002-10-14 19:44:54 UTC


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