Bug 71716 – Crash during first boot after installation

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 71716 - Crash during first boot after installation


Summary:	Crash during first boot after installation


Status:	RESOLVED DUPLICATE of bug 71721

Product:	gnome-core
Classification:	Deprecated
Component:	panel
Version:	1.4.x
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-02-16 22:41 UTC by sfoster
Modified:	2004-12-22 21:47 UTC

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

Description sfoster 2002-02-16 23:41:43 UTC

Package: gnome-panel
Severity: normal
Version: 1.4.0.4
Synopsis: Crash during first boot after installation
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel

Description:
I installed RedHat 7.2 on a Compaq E500 laptop. This error occured when gnome started on the first boot of the system after installation.


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)...
0x405af669 in __wait4 () from /lib/i686/libc.so.6

+ Trace 17865

#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
at malloc.c line 2878
#5 __libc_calloc
at malloc.c line 3844
#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
at eval.c line 41
#9 panel_widget_draw_icon
at eval.c line 41
#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
at eval.c line 41
#33 __libc_start_main
at ../sysdeps/generic/libc-start.c line 129
#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
at malloc.c line 2878
#5 __libc_calloc
at malloc.c line 3844
#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-02-16 18:41 -------

The original reporter (sfoster@ultranet.com) 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 Mark McLoughlin 2002-02-18 18:32:08 UTC

this is a bug in the gnome 1.4 panel. Moving to gnome-core where bugs
for this version live

Comment 2 Mark McLoughlin 2002-02-18 18:35:13 UTC


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