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 71216 - Damn panel crashes (panel Crash at 80.132.188.90)
Damn panel crashes (panel Crash at 80.132.188.90)
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-02-11 22:40 UTC by flim
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description flim 2002-02-11 22:40:45 UTC
Package: panel
Version: 1.4.0.4
Severity: 

>Synopsis: Damn panel crashes
>Class: sw-bug
System: redhat 7.2 fullinstall

>Description:
Panel crashes each time x starts. This is not a problem of applications being installed or updates - it's after every new install. System is redhat 7.2 running on dell p3 933 with 512 mb ram and some standart 32 mb graphics adapter (I always forget these names). After restarting panel on the console, there are no further problems with it.
My main problem on this problem is the "§$!§"$ bug tracking software - there should be something to disable it. So how to do it and stop it from going on my nerves each time x starts? I thought this is linux, not windows where you are forced to press some million buttons each time something crashes...not that convieniend for users like me that are not that familiar with x configuration :-(

>How-To-Repeat:
Start X.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-02-11 17:40 -------

The original reporter (flim@novadoc.de) 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 Roy-Magne Mo 2002-02-11 23:01:11 UTC

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