Description of problem: An open WPA2 authentication dialog does not block further dialogs. If the user is away from the console or too slow in entering a network key, a confusing stack of identical dialogs accumulates. Version-Release number of selected component (if applicable): NetworkManager-0.9.2-1.fc16.x86_64 How reproducible: Always, when an existing network key stops working. Steps to Reproduce: 1. Join a WPA2 protected network 2. Have authentication fail later, e.g. router failure or network passphrase changed 3. Do not interact with authentication dialog when it appears Actual results: Multiple dialogs will appear over time, apparently after a periodic timer expires. Expected results: Once an authentication dialog is open for a selected network, NetworkManager should stop firing more related UI events until the user chooses an action (such as continuing with the previous key, entering a new key, or canceling). Or at the very least, the stale dialog should be closed before opening a new one. Additional info: This happened for us on a network where the access point sporadically fails to authenticate clients after a few weeks of use (requiring an access point reboot to restore function).
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.
For what it's worth, this was fixed recently in upstream and is part of the NM 0.9.8 release in F18 and later.
Is 0.9.8 going to be pushed back to F17?