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 75166 - Panel crash and does not come back (panel Crash at 24.116.96.95)
Panel crash and does not come back (panel Crash at 24.116.96.95)
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-03-17 22:23 UTC by jfmiii
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jfmiii 2002-03-17 22:23:18 UTC
Package: panel
Version: 1.4.0.4
Severity: 

>Synopsis: Panel crash and does not come back
>Class: sw-bug
System: sony VAIO pentium 4 ,2.0Ghz ,Model PCV-RX571

>Description:
I have the computer drive split up 20 Gig for the windows XP that came installed and 60 Gig alloted for RedHat 7.2 . When I installed RedHat I set it up for English and Korean for my wife. When I updated The software using up2date The first time I selected everything. After completion I rebooted and the panel crashed. I subsequently reloaded red hat and this time it crashed after trying to switch back to english from Korean This is the third Time this has happened and I,m not realy sure what caused it each time but, after a Panel crash I do not know how to get the panel back without reloading redhat.......

>How-To-Repeat:
switching from English to Korean and back to english




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-03-17 17:23 -------

The original reporter (jfmiii@cableone.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 Wayne Schuller 2002-03-23 05:53:34 UTC

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