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 80436 - Crash when starting Gnome from new install
Crash when starting Gnome from new install
Status: RESOLVED DUPLICATE of bug 59500
Product: gnome-panel
Classification: Other
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-01 05:21 UTC by newzletterz
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description newzletterz 2002-05-01 05:23:06 UTC 
Package: gnome-panel
Severity: normal
Version: 1.4.0.4
Synopsis: Crash when starting Gnome from new install
Bugzilla-Product: gnome-panel
Bugzilla-Component: general

Description:
I just installed Redhat 7.2, I selected the "everything" option from the install, configured Eth0 with a static IP, and removed VNC and VNC server from the individual packages. The login type was ocnfigured as text, and the default GUI was ocnfigured as GNOME. Everything else was default. I input the username as "root" and pressed enter without a password. Since that faild, I logged in with a user account created from the installation, pinged www.yahoo.com and then startex X-windows. I got this error. Hope bug buddy gets you the info you need.


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 21542

  • #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_malloc
    at malloc.c line 2811
  • #6 g_malloc
    from /usr/lib/libglib-1.2.so.0
  • #7 gdk_window_foreign_new
    from /usr/lib/libgdk-1.2.so.0
  • #8 gwmh_init
    at eval.c line 41
  • #9 gwmh_root_put_atom_window
    at eval.c line 41
  • #10 gwmh_root_put_atom_window
    at eval.c line 41
  • #11 gwmh_task_notifier_remove_func
    at eval.c line 41
  • #12 gwmh_task_notifier_remove_func
    at eval.c line 41
  • #13 gwmh_root_put_atom_window
    at eval.c line 41
  • #14 gwmh_root_put_atom_window
    at eval.c line 41
  • #15 g_idle_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #16 g_main_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #17 g_main_iterate
    from /usr/lib/libglib-1.2.so.0
  • #18 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #20 main
    at eval.c line 41
  • #21 __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_malloc
    at malloc.c line 2811
  • #6 g_malloc
    from /usr/lib/libglib-1.2.so.0
  • #7 gdk_window_foreign_new
    from /usr/lib/libgdk-1.2.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-01 01:23 -------

The original reporter (newzletterz@hotmail.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 Heath Harrelson 2002-05-01 20:05:44 UTC 
Thank you for your bug report.  This particular crash is a known
problem that is being worked on.  Hopefully it will be fixed in GNOME
1.4.1.

In the meantime, you can try the gnome-libs and gnome-core packages 
available at http://www.gnome.org/~kmaraas and see if those help. If
you do choose to install these packages, it would be a really great
help to us if you report back the results.



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