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 79815 - panel segmentation falt on clean redhat install (panel Crash at 66.24.17.224)
panel segmentation falt on clean redhat install (panel Crash at 66.24.17.224)
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-25 00:54 UTC by Craig
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Craig 2002-04-25 00:55:13 UTC
Package: panel
Version: 1.4.0.4
Severity: 

>Synopsis: panel segmentation falt on clean redhat install
>Class: sw-bug
System: redhat 7.2 clean install intel processor

>Description:
Application "panel" (process 5793) has crashed due to a fatal error .
(Segmentation fault)

message appears after a clean redhat 7.2 install on intel system.

>How-To-Repeat:
cleanly installed redhat 7.2 on system.  load gnome via startx.  deleting all .gnome* files in $HOME seemed to fix the problem.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-04-24 20:55 -------

The original reporter (craigsjunk@yahoo.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, panel-maint@bugzilla.gnome.org.

Comment 1 Craig 2002-04-26 05:15:57 UTC
I found two solutions to this problem (other than manually reloading
the panel each time):

1. Remove the panel file in $HOME/.gnome/panel

Once the file is regererated by gnome, it works from then on for that
particular user.  The problem is repeated (on my machine) for each new
user added with via useradd -m; so $HOME/.gnome/panel must be removed
for each new user added.  


2. Upgrading from Xfree86 v3 to XFree86 v4

For some reason Redhat 7.2 decided to use Xfree86 v3 on clean install
instead of v4, as is typically done.  (RH 7.2 ships w/ both Xf86 v3 &
4).  So I reconfigured to use Xfree86 v4 via Xconfigurator --expert
--preferxf4.  Once I did this the problem went away--even for new
users created via useradd -m.  Perhaps this problem is limited to
Xfree86 v3.
Comment 2 Wayne Schuller 2002-05-31 13:24:11 UTC
you are right.. this is a known problem we are working on.

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