Bug 462846
| Summary: | system-config-bind/ modal dialog refuses to die | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | ritz <rkhadgar> | ||||||
| Component: | system-config-bind | Assignee: | Jaroslav Reznik <jreznik> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Cermak <mcermak> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 5.4 | CC: | azelinka, illtud.daniel, jason.vas.dias, mcermak, ovasik, rvokal, sputhenp | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | system-config-bind-4.0.3-5.el5 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-11-30 12:12:11 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 462847 | ||||||||
| Attachments: |
|
||||||||
Created attachment 317182 [details]
screenshot of the issue.
Not much to say other than 'me too'. It's a pretty badly behaved app all round, to be honest. This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". system-config-bind was designed never to allow a dialog to be closed successfully (return an "OK" response) if that dialog would insert invalid or erroneous data into a named configuration file . Call that "badly behaved" if you like, but that is the way it is. If you've any other examples of "badly behaved" I'll take a look at them . Jaroslav , I think this bug can probably be closed. The problem isn't that the application won't accept bad data (that's a good thing), it's just that when it recognises bad data there's nothing you can do about it except terminate the application. As ritz says: Expected results: The dialogue box should go away and the end user would be given chance to correct the mistake. Take a look at the screenshot - it's the 'DNS Name Error' dialogs that don't go away, and you can't get focus back to the data entry dialog to do anything about your bad data. (In reply to comment #5) > The problem isn't that the application won't accept bad data (that's a good > thing), it's just that when it recognises bad data there's nothing you can do > about it except terminate the application. As ritz says: > > Expected results: > The dialogue box should go away and the end user would be given chance to > correct the mistake. > > Take a look at the screenshot - it's the 'DNS Name Error' dialogs that don't go > away, and you can't get focus back to the data entry dialog to do anything > about your bad data. I agree - sane configuration is what we need but modal dialog that don't go away is really bad. If dialog insert invalid date there should be way to terminate application without saving invalid configuration, let user fix problem or some kind of recovery dialog asking user to reload valid configuration. So I'm not going to close this bug. 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-2011-1505.html |
Created attachment 317181 [details] patch Description of problem: When I give wrong NS name (eg, ".test.") while adding an NS record for a domain via system-config-bind, I get correct error dialog about null name that cannot be closed (there is only OK) - it is returning again and again and only solution is shutdown the GUI. Version-Release number of selected component (if applicable): system-config-bind-4.0.3-2.el5 How reproducible: always Steps to Reproduce: - Launch system-config-bind - Add a new zone by selecting Add -> Zone after right clicking "DNS Server" icon. - After the new zone was created, Right Click on the new zone -> Add -> NS Name Server. - Enter ".test." in the "Server Domain Name" field. - Click ok. - A dialogue box would pop up saying "Bad DNS Name: .test. - null label 1 not allowed." Click "OK" on the dialogue box. It would never go away. If we keep clicking on "OK", the dialogue box would duplicate. This is a bug and would be fixed. Actual results: While clicking "OK" on the dialogue box, it never go away and keeps poping up again and again and duplicates after some clicks. Expected results: The dialogue box should go away and the end user would be given chance to correct the mistake. Additional info: It seems gtk.entry captures the focus, and and focus_out event causes the the dialog to pop up. disabling grab_focus helps. This issue is also seen in upstream.