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 80047 - When starting gnome for the first time. (panel Crash at 67.83.136.74)
When starting gnome for the first time. (panel Crash at 67.83.136.74)
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-27 12:19 UTC by richiemeister
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description richiemeister 2002-04-27 12:20:21 UTC 
Package: panel
Version: 1.4.0.4
Severity: 

>Synopsis: When starting gnome for the first time.
>Class: sw-bug
System: Gnome / new user acct

>Description:
When starting a new account for the first time, it crashed. I am using Linux 7.2. The error message says "Application "panel" (process 1599) has crashed due to a fatal error. (Segmentation fault)".

>How-To-Repeat:
Logged into the user's account for the first time. This is a new user.




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

The original reporter (richiemeister@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, panel-maint@bugzilla.gnome.org.
Comment 1 Heath Harrelson 2002-04-27 20:29:50 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 ***