Hide Forgot
Description of problem: All attempts to connect to a wireless network with NetworkManager are in vain because the "apply" button which enables changes in configuration is always "greyed out". Version-Release number of selected component (if applicable): [msevior@seviorlap2 ~]$ rpm -qa | grep -i NetworkManager NetworkManager-pptp-0.8.1-1.fc14.i686 NetworkManager-openvpn-0.8.1-1.fc14.i686 NetworkManager-glib-0.8.1-10.git20100831.fc14.i686 NetworkManager-0.8.1-10.git20100831.fc14.i686 NetworkManager-gnome-0.8.1-10.git20100831.fc14.i686 NetworkManager-vpnc-0.8.1-1.fc14.i686 [msevior@seviorlap2 ~]$ How reproducible: 100% Steps to Reproduce: 1. Boot computer in a region with WiFi coverage 2. When NetworkManager discovers the network the "apply" button is grey 3. No matter what you type anywhere in the diaglog box, the apply button is always grey. Actual results: The apply button is always grey. Expected results: I expect the button to be ative to allow me to enter the network key. Additional info:
You don't mostly need to go to nm-connection-editor to get connected. Just clicking on a network name in nm-applet should present you with a dialog to enter a password and connect. Nonetheless, when you edit the connection in the editor, you will have to fill some necessary information in order to Apply button gets sensitive. They are namely the SSID in 'Wireless' tab and Password on 'Wireless Security' tab. Would you include a screenshot if this doesn't help.
Created attachment 475381 [details] screenshot showing NM editing dialog
Created attachment 475382 [details] screenshot showing connect dialog from the NM applet
Hi Jirka, Thanks very much for taking a look at this bug. Actually neither the connection dialog from NM nor the connection editor from NM allow me to make changes to the wireless settings. I've attached two screenshots showing this. I tired running NM as root but I also got exactly the same result. Both the "apply" and "connect" buttons were always greyed out.
Further typing in the appropriate key in either dialog does not ungrey the "connect" or "apply" buttons.
(In reply to comment #2) The 'Wireless' tab looks fine. But, the problem will be in that you have not (correctly) filled WEP key in 'Wireless Security' tab. The same is true for the second screenshot. When you fill the Key of correct length, the 'Connect' button will sensitize. Generally, WEP password can be one of these: * WEP hex key - string of hexadecimal chars of length 10 or 26 * WEP ascii key - string of 5 or 13 characters * WEP passphrase - string up to 63 characters The 1. an 2. are input as Wireless Security type of "WEP 40/128-bit Key (Hex or ASCII)". For WEP passphrase, you have to select "WEP 128-bit Passphrase". So, find out what key type your AP uses and configure NM with the proper key.
I'm seeing the same issue when I try configuring a new OpenVPN connection from NM. NetworkManager-openvpn-0.8.1-1.fc14.x86_64 NetworkManager-gnome-0.8.1-10.git20100831.fc14.x86_64 NetworkManager-0.8.1-10.git20100831.fc14.x86_64 NetworkManager-pptp-0.8.1-1.fc14.x86_64 NetworkManager-glib-0.8.1-10.git20100831.fc14.x86_64 NetworkManager-vpnc-0.8.1-1.fc14.x86_64 NetworkManager-openconnect-0.8.1-1.fc14.x86_64 Attaching a screenshot with the VPN window and the grayed out apply button
Created attachment 476631 [details] screenshot showing the OpenVPN window
Basically, the button is made sensitive *after* all necessary information is input. Adrian, you have not selected any CA Certificate.
Got it, thank you.
A VERY hard to spot problem is when adding IP addresses or routes. If a new line has been created but left blank. 1. In the Routes or IPv4 tab, click Add 2. Highlight (or edit) the existing address 3. The Apply button is unavailable I'd hope for some visual cue that the problem lies in the empty line, three zero-length strings should be a hint to nm-connection-editor that the input is invalid and can be discarded.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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