Description of problem: after recent upgrades in network manager(not sure which one) my system posts msg "Activation of network failed" Investigation into network-profile shows none or just some of the required addresses ( ipv4, ipv6, dns) have worked with provider multiple times with no success.HELP Version-Release number of selected component (if applicable): How reproducible: click on the globe for firefox Steps to Reproduce: 1. 2. 3. Actual results: Activationof network failed msg. Expected results: valid network connection Additional info: 12 systems either through switch or directly attached to modems. have exhausted hardwre possibilities.
resolved via following process: 1) remove all connection profiles. 2) had ip rmove phone from network. 3) poweroff all systems, cisco switch, and modem. 4) pwr-up and reboot modem. 5) pwr-up the switch. 6) pwr-up and login to all systems. 7) display a blank connectio profile (yes..blank) and hit add. this causes eno*-connection. do it out of sequence and your back to "Activation of network"!!
Perhaps the same problem, but I was installing Fedora 28 KDE Spin on a Lenovo ThinkCentre M92p with a RTL8191SU USB Wireless-N interface. NetworkManager connected properly during and after the installation with these NetworkManager RPMS: NetworkManager-vpnc-1.2.4-7.fc28.x86_64 NetworkManager-libreswan-1.2.4-6.fc28.x86_64 NetworkManager-wwan-1.10.6-1.fc28.x86_64 NetworkManager-team-1.10.6-1.fc28.x86_64 NetworkManager-bluetooth-1.10.6-1.fc28.x86_64 NetworkManager-pptp-1.2.6-1.fc28.x86_64 NetworkManager-1.10.6-1.fc28.x86_64 NetworkManager-openconnect-1.2.4-9.fc28.x86_64 NetworkManager-config-connectivity-fedora-1.10.6-1.fc28.noarch NetworkManager-wifi-1.10.6-1.fc28.x86_64 NetworkManager-libnm-1.10.6-1.fc28.x86_64 NetworkManager-openvpn-1.8.2-1.fc28.x86_64 NetworkManager-l2tp-1.2.10-1.fc28.x86_64 NetworkManager-adsl-1.10.6-1.fc28.x86_64 Then I did a 'dnf update' and rebooted the system. After the system restarted, NetworkManager would no longer connect to my WiFi network. I kept getting a password prompt. The updated RPMs are: NetworkManager-team-1.10.8-1.fc28.x86_64 NetworkManager-vpnc-1.2.4-7.fc28.x86_64 NetworkManager-libreswan-1.2.4-6.fc28.x86_64 NetworkManager-wifi-1.10.8-1.fc28.x86_64 NetworkManager-pptp-1.2.6-1.fc28.x86_64 NetworkManager-1.10.8-1.fc28.x86_64 NetworkManager-bluetooth-1.10.8-1.fc28.x86_64 NetworkManager-openconnect-1.2.4-9.fc28.x86_64 NetworkManager-openvpn-1.8.4-1.fc28.x86_64 NetworkManager-adsl-1.10.8-1.fc28.x86_64 NetworkManager-wwan-1.10.8-1.fc28.x86_64 NetworkManager-l2tp-1.2.10-1.fc28.x86_64 NetworkManager-libnm-1.10.8-1.fc28.x86_64 NetworkManager-config-connectivity-fedora-1.10.8-1.fc28.noarch Here are the log entries related to the connection attempt: Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.0866] device (wlp0s20u3): Activation: starting connection '2000 Cove Creek Road' (0a79aa30-9599-428b-93bc-a08d33b5d523) Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.0871] device (wlp0s20u3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.0873] manager: NetworkManager state is now CONNECTING Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.0879] device (wlp0s20u3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.0883] device (wlp0s20u3): Activation: (wifi) access point '2000 Cove Creek Road' has security, but secrets are required. Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.0884] device (wlp0s20u3): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.0886] sup-iface[0x557a38372170,wlp0s20u3]: wps: type pbc start... Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.0991] device (wlp0s20u3): supplicant interface state: inactive -> scanning Jun 03 03:50:28 localhost.localdomain kdeinit5[1252]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" Jun 03 03:50:28 localhost.localdomain plasmashell[1311]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1147] device (wlp0s20u3): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1153] device (wlp0s20u3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1155] device (wlp0s20u3): Activation: (wifi) connection '2000 Cove Creek Road' has security, and secrets exist. No new secrets needed. Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1155] Config: added 'ssid' value '2000 Cove Creek Road' Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1156] Config: added 'scan_ssid' value '1' Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1156] Config: added 'bgscan' value 'simple:30:-80:86400' Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1156] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256' Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1156] Config: added 'auth_alg' value 'OPEN' Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1156] Config: added 'psk' value '<hidden>' Jun 03 03:50:28 localhost.localdomain NetworkManager[851]: <info> [1527997828.1156] Config: added 'ieee80211w' value '1' Jun 03 03:50:38 localhost.localdomain NetworkManager[851]: <info> [1527997838.1059] device (wlp0s20u3): supplicant interface state: scanning -> associating Jun 03 03:50:38 localhost.localdomain NetworkManager[851]: <info> [1527997838.4452] device (wlp0s20u3): supplicant interface state: associating -> associated Jun 03 03:50:38 localhost.localdomain NetworkManager[851]: <info> [1527997838.4521] device (wlp0s20u3): supplicant interface state: associated -> 4-way handshake Jun 03 03:50:38 localhost.localdomain NetworkManager[851]: <info> [1527997838.4594] device (wlp0s20u3): supplicant interface state: 4-way handshake -> disconnected Jun 03 03:50:38 localhost.localdomain NetworkManager[851]: <info> [1527997838.4606] device (wlp0s20u3): Activation: (wifi) disconnected during association, asking for new key Jun 03 03:50:38 localhost.localdomain NetworkManager[851]: <info> [1527997838.4608] device (wlp0s20u3): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Jun 03 03:50:38 localhost.localdomain NetworkManager[851]: <info> [1527997838.5596] device (wlp0s20u3): supplicant interface state: disconnected -> inactive Jun 03 03:51:50 localhost.localdomain NetworkManager[851]: <warn> [1527997910.5037] device (wlp0s20u3): User canceled the secrets request. Jun 03 03:51:50 localhost.localdomain NetworkManager[851]: <info> [1527997910.5037] device (wlp0s20u3): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Jun 03 03:51:50 localhost.localdomain NetworkManager[851]: <info> [1527997910.5042] manager: NetworkManager state is now DISCONNECTED Jun 03 03:51:50 localhost.localdomain NetworkManager[851]: <warn> [1527997910.5048] device (wlp0s20u3): Activation: failed for connection '2000 Cove Creek Road' Jun 03 03:51:50 localhost.localdomain NetworkManager[851]: <info> [1527997910.5060] device (wlp0s20u3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') I will attach a zip file with relevant log and command output.
Created attachment 1447141 [details] Logs and command output attempting to connect RT8191SU USB with NM
Doing a 'dnf history rollback' resolved the issue.
(In reply to Israel J Pattison from comment #4) > Doing a 'dnf history rollback' resolved the issue. Did you update and rollback wpa_supplicant as well? If so, probably this is caused by PMF support in wpa_supplicant (see bug 1582407).
Can you please try running: nmcli connection modify '2000 Cove Creek Road' wifi-sec.pmf disable and reconnecting?
my procedure proved a successful work around until the following NetworkManager update resolved the problem. as indicated; not using wifi please stop sending email requests for update.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.