Description of problem: If you delete all connections in nmtui and then select 'Activate a connection', then nmtui exit with non-friendly error message. Version-Release number of selected component (if applicable): NetworkManager-0.9.10.0-1.git20140704.fc21 How reproducible: always Steps to Reproduce: 1. nmtui 2. Edit a connection 3. delete all connections there 4. Exit nmtui 5. start nmtui again 6. select 'Activate a connections' Actual results: nmtui:ERROR:nmt-newt-listbox.c:333:update_active_internal: assertion failed: (priv->active >= 0 && priv->active < priv->entries->len) Aborted And end with ncurses dialog still drawn in screen, which looks pretty ugly. Expected results: Either clear screen and write nice error message. Or show dialog with empty list of connections to activate. (I prefer this one)
Getting the same, el7 NetworkManager-0.9.9.1-13.git20140326.4dba720.el7.x86_64
My problem may be related to this being a cloned virtual host.. mac address duplication or mismatch perhaps.
The bug has been fixed upstream: master: 5aa204e tui: fix a crash when connection list for activation is empty (rh #1119663) nm-0-9-10: 5e621c4 tui: fix a crash when connection list for activation is empty (rh #1119663) We will push the fix to Fedora in a next build.
NetworkManager-1.0.2-1.fc22,network-manager-applet-1.0.2-1.fc22,NetworkManager-openconnect-1.0.2-1.fc22,NetworkManager-openvpn-1.0.2-1.fc22,NetworkManager-vpnc-1.0.2-1.fc22,NetworkManager-openswan-1.0.2-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/NetworkManager-1.0.2-1.fc22,network-manager-applet-1.0.2-1.fc22,NetworkManager-openconnect-1.0.2-1.fc22,NetworkManager-openvpn-1.0.2-1.fc22,NetworkManager-vpnc-1.0.2-1.fc22,NetworkManager-openswan-1.0.2-1.fc22
This is fixed in 0.9.10.2, and thus has been pushed to Fedora 21 already.
Package NetworkManager-1.0.2-1.fc22, NetworkManager-openconnect-1.0.2-1.fc22, NetworkManager-vpnc-1.0.2-1.fc22, network-manager-applet-1.0.2-1.fc22, NetworkManager-openvpn-1.0.2-1.fc22, NetworkManager-openswan-1.0.2-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-1.0.2-1.fc22 NetworkManager-openconnect-1.0.2-1.fc22 NetworkManager-vpnc-1.0.2-1.fc22 network-manager-applet-1.0.2-1.fc22 NetworkManager-openvpn-1.0.2-1.fc22 NetworkManager-openswan-1.0.2-1.fc22' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7767/NetworkManager-1.0.2-1.fc22,network-manager-applet-1.0.2-1.fc22,NetworkManager-openconnect-1.0.2-1.fc22,NetworkManager-openvpn-1.0.2-1.fc22,NetworkManager-vpnc-1.0.2-1.fc22,NetworkManager-openswan-1.0.2-1.fc22 then log in and leave karma (feedback).
NetworkManager-1.0.2-1.fc22, NetworkManager-openconnect-1.0.2-1.fc22, NetworkManager-vpnc-1.0.2-1.fc22, network-manager-applet-1.0.2-1.fc22, NetworkManager-openvpn-1.0.2-1.fc22, NetworkManager-openswan-1.0.2-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Here the problem is you deleted all default parameters including mac address. Solution is.. Do not delete the mac address or you can keep it empty so that it can select default mac address in backend. But never put any value here axcept default mac address.
(In reply to monu from comment #8) > Here the problem is you deleted all default parameters including mac(device) address. > > Solution is.. Do not delete the mac address(device) or you can keep it empty so that it can select default mac address in backend. But never put any value here axcept default mac address. There mac address represented by "device".