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 76037 - gnome panel crash bug
gnome panel crash bug
Status: RESOLVED DUPLICATE of bug 59481
Product: gnome-core
Classification: Deprecated
Component: panel
1.4.x
Other other
: Normal critical
: 1.4.1
Assigned To: Panel Maintainers
Panel Maintainers
: 82547 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-03-23 03:20 UTC by npy
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description npy 2002-03-23 08:48:42 UTC
Package: GConf
Severity: major
Version: 1.4.0.4
Synopsis: gnome panel crash bug
Bugzilla-Product: GConf
Bugzilla-Component: gconf

Description:

I have this random behaviour of GNOME crashing immediately upon logining in.
It happens about once every 3 logins.

This crashing behaviour only happens on my Dell Inspiron 8100 Laptop.
It has a Nvidia Geforce32 VGA. It has never happen on my Desktop, 
which is running a SiS6362 chipset.

Once I get past the GNOME initialization process (and the panel shows up),
the X-window will be stable. If, on the other hand, the crash occurs, it will repeatedly
crash itself, even with re-login through the XDM. 

What's more, the crash will repeat itself even if I do something like
	init 1
	init 5

The only way to correct the problem is to reboot and hope for the best.
Most of all time, a single reboot is what it takes, though sometimes it takes
a few tries because the system is rid of its demons.



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
  • #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 create_menu_at
    at eval.c line 41
  • #5 main
    at eval.c line 41
  • #6 __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 create_menu_at
    at eval.c line 41
  • #5 main
    at eval.c line 41
  • #6 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __strtol_internal
    at eval.c line 36




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

The original reporter (npy@vaccius.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, hp@redhat.com.

Comment 1 Havoc Pennington 2002-03-23 14:57:09 UTC
See also:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=55119

This is a very common bug, which seems to happen only on certain
hardware (laptops mostly?), and only on Red Hat 7.2, and no one has
figured out yet.
Comment 2 Luis Villa 2002-05-31 01:41:26 UTC
*** Bug 82547 has been marked as a duplicate of this bug. ***
Comment 3 Kjartan Maraas 2002-07-29 13:25:53 UTC
Please try the latest 1.4.x release of gnome-libs and gnome-core. We
haven't seen this reported in the last few releases.

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