Red Hat Bugzilla – Bug 462847
system-config-bind/ modal dialog refuses to die
Last modified: 2009-12-18 01:24:36 EST
+++ This bug was initially created as a clone of Bug #462846 +++
Created an attachment (id=317181)
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):
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.
While clicking "OK" on the dialogue box, it never go away and keeps poping up again and again and duplicates after some clicks.
The dialogue box should go away and the end user would be given chance to correct the mistake.
It seems gtk.entry captures the focus, and and focus_out event causes the the dialog to pop up. disabling grab_focus helps.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.