Bug 81414 – Crash beim Starten von X

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 81414 - Crash beim Starten von X


Summary:	Crash beim Starten von X


Status:	RESOLVED DUPLICATE of bug 77540

Product:	gnome-desktop
Classification:	Core
Component:	libgnome-desktop
Version:	unspecified
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-05-10 22:21 UTC by elvis.altherr
Modified:	2004-12-22 21:47 UTC

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

Description elvis.altherr 2002-05-10 22:12:17 UTC

Package: gnome-desktop
Severity: normal
Version: 1.4.0.4
Synopsis: Crash beim Starten von X
Bugzilla-Product: gnome-desktop
Bugzilla-Component: libgnome-desktop

Description:
beim Starten von X Window unter Red Hat 7.2 erschien beim Aufstarten vorhergende  Meldung


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

+ Trace 21993

#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-05-10 18:12 -------

The original reporter (elvis.altherr@elvisaltherr.ch) 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-desktop-maint@bugzilla.gnome.org.

Comment 1 Kjartan Maraas 2002-05-11 09:02:27 UTC

Please try gnome-libs-1.4.1.6 and gnome-core-1.4.0.8 or newer. You'll
find RPMs of these packages at http://www.gnome.org/~kmaraas if you
can make use of those. It would be nice if you could report back here
if this fixes the problem for you.

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