Bug 78014 - rhn-applet chashes panel -- login impossible
rhn-applet chashes panel -- login impossible
Status: CLOSED DUPLICATE of bug 75138
Product: Red Hat Linux
Classification: Retired
Component: rhn-applet (Show other bugs)
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Daniel Veillard
Depends On:
  Show dependency treegraph
Reported: 2002-11-17 09:56 EST by John Franks
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-17 09:56:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Franks 2002-11-17 09:56:34 EST
Description of Problem:  If the rhn-applet has been moved to a new panel (of
some types) then login is impossible.  The panel application crashes producing a
dialog and continues to crash repeatedly.  Restarting the X server is the only
way I have found to get out.

Version-Release number of selected component (if applicable):
rhn-applet-2.0.0-28, gnome-panel-2.0.6-9, GConf2-1.2.1-3, GConf-1.0.9-6

How Reproducible: Consistently if steps are followed.  I have done this on
multiple RH8.0 machines

Steps to Reproduce:
1. Configure a rhn-applet, i.e. make sure the configuration dialog has been run
and the blue check mark button is displayed.
2. Create a new sliding panel and place it vertically on the right edge of the

3. Using the middle mouse button drag the rhn-applet by the small hatched area
on its left and drop it in the new panel.

4. Logout and attempt to login again.

Actual Results: 
Panel crash and bug-buddy dialog appears.  When the panel attempts to respawn it
crashes again.  This repeats.  

Expected Results:
Normal login

Additional Information:
It seems crucial that the new panel be on the side.  I don't know if it needs to
be a sliding panel.
Comment 1 Chip Turner 2002-11-18 12:33:18 EST

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

Note You need to log in before you can comment on or make changes to this bug.