Description of problem: When I boot my system and am on a wired connection, NM keeps attempt to connect to a wireless network as well and keeps prompting me for the WPA2 key. I have to disable wireless networking in order to stop this behavior. Version-Release number of selected component (if applicable): (mcpierce@mcpierce-laptop:~)$ rpm -q NetworkManager NetworkManager-0.8.9997-5.git20110702.fc15.x86_64 How reproducible: 100% Steps to Reproduce: 1. Boot the system with a wired connection. 2. Log into a desktop. 3. Actual results: Dialogs keep popping up asking for a WPA2 key. Expected results: NM should see a wired connection and not attempt to connect to a wireless network. Additional info:
You probably have a Wi-Fi connection that is marked for auto connection. So NM tries to connect that connection profile. If you want to prevent a connection from auto-connecting, run nm-connection-editor and uncheck "Connect automatically". List connections and their autoconnect setting with: $ nmcli -f name,uuid,autoconnect con list See also bug 717665.
same pb here. doesn't look ok to mee that if by error, I clik on one wifi neighbour network (which I don't have credential for), I will be poped forever. I should be able to right click to disable it. If I'm not in front of the pc, I will even have multiple popup for the same network, whcih sounds like a bug for me.
I am having the same problem here. > You probably have a Wi-Fi connection that is marked for auto connection. So > NM tries to connect that connection profile. > If you want to prevent a connection from auto-connecting, run > nm-connection-editor and uncheck "Connect automatically". Unchecking "autoconnect" seems to be a viable workaround for this problem. But it's broken behavior. NetworkManager should know that wired connections are almost always preferable over wireless connections. Given that "the goal of NetworkManager is to make networking Just Work with a minimum of user hassle", users shouldn't be bothered with Wifi passwords when the wired connection is up. "autoconnect" means something else to me - it means that if I unplug the wired network, and the configured Wifi is available, it would be connected automatically. This is exactly how NM works on my old laptop running GNOME2 under OpenSUSE 11.4 at home. On the contrary, when "autoconnect" is off, a user would need to manually activate network using some tool (e.g. nm-applet) before a connection was attempted, whether or not wired network was on. (Btw: I never set the "autoconnect" flag on my machine - seems to have been set by GNOME3/nm-applet or whatever automatically).
(In reply to comment #1) > If you want to prevent a connection from auto-connecting, run > nm-connection-editor and uncheck "Connect automatically". This is only half the solution. With "Connect automatically" unset, the Wifi connection won't be activated by default. But once the user activated it, there is no way to deactivate it again when the computer has been plugged back into the Wired LAN except for using the kill switch, at least not in nm-applet. It can be done with "nmcli con down id <ID>", but that's not exactly user-friendly.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
I also had the same version problems in 19 and 20. Is it possible to have auto-connect off for wireless until the user sets it to on?
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
I see no evidence that this broken behavior has been fixed in F20 or F21. I have currently set autoconnect=off for my Wifi connections, but that's not the ultimate solution (which would be autoconnect=on iff there is no active wired connection).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.