Created attachment 499672 [details] non modal dialog Description of problem: When a third layer dialog appears, you can click on the dialog above it. Doing so returns focus to that dialog even though it is unusable. Version-Release number of selected component (if applicable): subscription-manager-0.95.5.18-1.git.3.7e444c3.el5 subscription-manager-firstboot-0.95.5.18-1.git.3.7e444c3.el5 subscription-manager-gnome-0.95.5.18-1.git.3.7e444c3.el5 How reproducible: always Steps to Reproduce: There are many ways to do this. You just need a dialog that is on top of a dialog. Here is one way: 1. Get a box with rhsm installed. 2. fire up subscription-manager-gui 3. Click "Register system" 4. Enter in invalid username and passwords and click register 5. When pop up error happens, click on the registration dialog. Actual results: Registration dialog receives focus. Registration dialog is unusable and not responsive to clicks. Expected results: The error dialog remains on top with focus until it is cleared by the user. Additional info: Happens on all branches of rhsm.
Moving out to 6.2. The code change looked to be more complicated than it's worth to fix in the 5.7 RC.
*** Bug 737696 has been marked as a duplicate of this bug. ***
Went as far into this issue as I dared, all errorWindow and handle_gui_exception calls now specify a parent window which should associate the dialog with it and prevent anything from hiding it away. Fixed in subscription-manager.git master 14460bc1eae88da8d20e21bb216a662cc468517e. Will appear in 0.98.4.
I've tested this with both the register dialog and the facts dialog, this now works and you cannot change focus within the program without clearing the error. marking VERIFIED. subscription-manager-gnome-0.98.5-1.git.2.cd86f84.el5_7
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0154.html