Description of problem: It takes very long time to establish wifi connection after I start my computer. The dropdown list of the network applet icon lists many different networks (wireless). Network settings > Wireless list my desired wifi connection as out of range. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Restart. 2. Pay attention to the wifi applet icon. 3. Wait few minutes for the connection to establish. Actual results: The icon indicates wifi connection has not been established. Expected results: Wifi connection is established within seconds after full system boot. Additional info: Thinkpad T500
I can now confirm that the problem is desktop environment agnostic. It was present on GNOME and LXDE (sessions of one Fedora 18 install) and LXDE (a separate Fedora 18 install).
Reproducibility: It happens at most of my system starts, though not always. Also when I go to Network Settings > Connect to a Hidden ... > select my usual wifi connection name instead of the "New" = it starts connecting immediately and never fails to connect this way.
When NetworkManager is not connecting correctly, can you run the 'dmesg' command and post the last 30 or 40 lines?
Created attachment 751809 [details] return of dmesg when the wifi connects after a long time I have pasted more than 40 lines because some earlier lines mentioned "Intel". I have no idea whether it is significant. Also: Sometimes during the boot process a "TSC calibration failed" message flashes for a short period of time from behind the Fedora logo. I cannot confirm whether it coincides with the wifi misbehavior.
Created attachment 752802 [details] return of dmesg when the wifi connects after a long time, a different os install with LXDE
Nothing has changed since I reported the bug. Also: ~$ systemd-analyze blame 31.452s NetworkManager-wait-online.service
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
Created attachment 865672 [details] dmesg ipv6 modification in /etc/sysctl.conf
Created attachment 865673 [details] ipv6.disable=1, no other ipv6-related setting changes
Created attachment 865675 [details] untouched ipv6 configuration case 3
Created attachment 865676 [details] untouched ipv6 configuration case 4
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.