Bug 83641 – Panel Crash (Fatal) after relog

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 83641 - Panel Crash (Fatal) after relog


Summary:	Panel Crash (Fatal) after relog


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-05-31 02:57 UTC by x40ozbaby
Modified:	2004-12-22 21:47 UTC

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

Description x40ozbaby 2002-05-31 02:52:17 UTC

Package: gnome-panel
Severity: major
Version: 1.4.0.4
Synopsis: Panel Crash (Fatal) after relog
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel

Description:
Booted into root then on relog on a users account the panel had a fatal crash.


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)...
0x405893b9 in wait4 () from /lib/libc.so.6

+ Trace 23071

#0 wait4
from /lib/libc.so.6
#1 __DTOR_END__
from /lib/libc.so.6
#2 gnome_segv_handle
from /usr/lib/libgnomeui.so.32
#3 <signal handler called>
#4 chunk_alloc
from /lib/libc.so.6
#5 calloc
from /lib/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/libc.so.6
#0 wait4
from /lib/libc.so.6
#1 __DTOR_END__
from /lib/libc.so.6
#2 gnome_segv_handle
from /usr/lib/libgnomeui.so.32
#3 <signal handler called>
#4 chunk_alloc
from /lib/libc.so.6
#5 calloc
from /lib/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-05-30 22:52 -------

The original reporter (x40ozbaby@mac.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 Kjartan Maraas 2002-05-31 16:15:16 UTC

Please try gnome-libs-1.4.1.7 and gnome-core-1.4.0.8 or newer. I've
made RPMs available at http://www.gnome.org/~kmaraas if you can make
use of those. Please report back here if this fixes the problem or not.

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