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 80104 - Panel crashes at start time (panel Crash at 66.169.128.67)
Panel crashes at start time (panel Crash at 66.169.128.67)
Status: RESOLVED DUPLICATE of bug 69333
Product: gnome-core
Classification: Deprecated
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-04-28 06:05 UTC by eantho1
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description eantho1 2002-04-28 06:06:08 UTC 
Package: panel
Version: 1.4.0.4
Severity: 

>Synopsis: Panel crashes at start time
>Class: sw-bug
System: 486 66Mhz; 44 MB; running Red Hat 7.2

>Description:
At boot or startup time the panel program aborts and I get an error window saying application fatal error, process 4242 crashed.  It has been doing so since I installed Red Hat 7.2.  Packages were selected by default.

>How-To-Repeat:
Every time at boot or startx time. I did nothing special.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-04-28 02:06 -------

The original reporter (eantho1@charter.net) 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, panel-maint@bugzilla.gnome.org.
Comment 1 Heath Harrelson 2002-04-28 22:46:54 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 69333 ***