Created attachment 854047 [details] Log Excerpt (repeats thousands of times) Description of problem: When a NetworkManager connection exists that requires credentials, but credentials are not available and cannot be requested, NetworkManager SAYS that it marks the connection invalid, but then IMMEDIATELY tries to open the connection again. This causes NetworkManager to use 100% CPU, rsyslog to use significant CPU (and log thousands upon thousands of lines of failures), and other subsystems such as the firewall system to use copious amounts of system resources. I discovered this on a fresh F20 install when I simply log in, connect to wireless, restart and leave the system at the login screen. My laptop fan spun up which led me to investigate why the CPU was so hot. Version-Release number of selected component (if applicable): NetworkManager-1:0.9.9.0-25.git20131003.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. Connect to a wireless network which requires authentication (mine uses PEAP/MSCHAPv2) 2. Restart, do not log into Gnome 3. Use another TTY to observe NetworkManager Actual results: NetworkManager repeatedly attempts to connect to the network, finds that it doesn't have the necessary credentials, and says that it is marking the connection as invalid. Rinse/repeat. Expected results: NetworkManager finds that the credentials are invalid ONCE, and gives up on that connection as it should. Additional info:
I believe this has now been fixed upstream by danw's patches for bug 1029480 (danw/autoconnect branch merge on 2014-01-23). It should appear in Fedora builds soon.
*** Bug 1052337 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.