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 65519 - panel crashes on start to runlevel 5 (panel Crash at 130.231.69.120)
panel crashes on start to runlevel 5 (panel Crash at 130.231.69.120)
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: 2001-11-27 18:05 UTC by mikko.angerman
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description mikko.angerman 2001-11-27 18:05:52 UTC 
Package: panel
Version: 1.4.0.4
Severity: 

>Synopsis: panel crashes on start to runlevel 5
>Class: sw-bug
System: Piii450/64 Acer Travelmate laptop, RedHat 7.2

>Description:
I get error message when strating to initlevel 5 that "panel" has crashed due to fatal error (segmentation fault).

Panel do not show any "icons", just blank bar.



>How-To-Repeat:
-install RH7.2 with "laptop" config
-reboot to runlevel 5-all's well
-to get more space to my 800x600 display I "right click" the panel and select "tiny" iconside to reduce panel size
-panel reduces
-shutdown normally
-boot normally next time to runlevel 5
-at the final steps panel error message appears!!!




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-11-27 13:05 -------

The original reporter (mikko.angerman@oulu.fi) 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 Kjartan Maraas 2002-01-25 16:50:09 UTC 
Please try the latest (1.4.x) version of gnome-core and gnome-libs
from http://download.gnome.org/ Contact me if you need RPMS.

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