Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 462846 - system-config-bind/ modal dialog refuses to die
system-config-bind/ modal dialog refuses to die
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: system-config-bind (Show other bugs)
5.4
All Linux
medium Severity medium
: rc
: ---
Assigned To: Jaroslav Reznik
Martin Cermak
:
Depends On:
Blocks: 462847
  Show dependency treegraph
 
Reported: 2008-09-19 07:17 EDT by ritz
Modified: 2013-04-12 15:53 EDT (History)
7 users (show)

See Also:
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 07:12:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch (476 bytes, patch)
2008-09-19 07:17 EDT, ritz
no flags Details | Diff
screenshot of the issue. (60.33 KB, image/png)
2008-09-19 07:22 EDT, ritz
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1505 normal SHIPPED_LIVE system-config-bind bug fix update 2011-11-30 12:11:23 EST

  None (edit)
Description ritz 2008-09-19 07:17:25 EDT
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.
Comment 1 ritz 2008-09-19 07:22:14 EDT
Created attachment 317182 [details]
screenshot of the issue.
Comment 2 illtud 2009-02-24 05:08:47 EST
Not much to say other than 'me too'. It's a pretty badly behaved app all round, to be honest.
Comment 3 RHEL Product and Program Management 2009-03-26 12:57:01 EDT
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 "?".
Comment 4 Jason Vas Dias 2009-05-16 01:21:11 EDT
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.
Comment 5 illtud 2009-05-16 12:11:48 EDT
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.
Comment 6 Jaroslav Reznik 2009-05-18 03:56:20 EDT
(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.
Comment 19 errata-xmlrpc 2011-11-30 07:12:11 EST
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

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