Description of problem: It is far too easy to end up with an invisible Network Configuration window _behind_ the full-screen firstboot window. When this happens the UI seems to be locked up locked up. Steps to Reproduce: 1. IPL from CDs 2. Click [Change Network Configuration] from firstboot's network configuration page 3. Click [Forward] on network configuration page Actual results: The firstboot full-screen window is displayed, but mouse is ineffective. UI appears locked up. <alt-tab> will bring the Network configuration window back to the surface. User must close the Network Configuration using the window frame's [X] button before clicking [Forward] Expected results: Either: - Clicking [Next] confirms and commits any outstanding network configuration changes - the Network Configuration window acts as a modal window and remains on the surface until explicitly closed (a commit button would make interaction more intuitive). Additional info: Not a regression, symptom also observed with RHEL5.3 Recovery: <alt-tab> brings the Network Configuration window back to the surface.
rich - this has been formally proposed for RHEL 5.5.
fixed in version 1.4.27.8
Stratus, can you test this with RHEL5.5 Beta and share your results? Thanks.
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~ RHEL 5.5 Beta has been released! There should be a fix present in this release that addresses your request. Please test and report back results here, by March 3rd 2010 (2010-03-03) or sooner. Upon successful verification of this request, post your results and update the Verified field in Bugzilla with the appropriate value. If you encounter any issues while testing, please describe them and set this bug into NEED_INFO. If you encounter new defects or have additional patch(es) to request for inclusion, please clone this bug per each request and escalate through your support representative.
Specific issue has been addressed: Network Configuration window stays on top with RHEL5.5 Beta. See bug 566739 for ancillary issues discovered while testing.
Moving to VERIFIED as per comment #12
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0314.html