Using a brcmfmac device, I can no longer connect to any wifi networks as of NetworkManager 1:1.4.0-1.fc25.x86_64; downgrading to 1:1.4.0-0.5.git20160621.072358da.fc25.x86_64 restores things. I had to tether through my phone to be able to downgrade. It seems to be treating a failure to set the MAC address as fatal: NetworkManager[1082]: <info> [1472550314.3189] device (wlp58s0): Activation: starting connection '[ESSID]' ([UUID]) NetworkManager[1082]: <info> [1472550314.3190] device (wlp58s0): state change: disconnected -> prepare (reason 'none') [30 40 0] NetworkManager[1082]: <warn> [1472550314.8215] device (wlp58s0): set-hw-addr: new MAC address [MAC] not successfully set to set-cloned (permanent) kernel: IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready NetworkManager[1082]: <info> [1472550314.8226] device (wlp58s0): state change: prepare -> failed (reason 'none') [40 120 0] NetworkManager[1082]: <warn> [1472550314.8231] device (wlp58s0): Activation: failed for connection '[ESSID]' NetworkManager[1082]: <info> [1472550314.8249] device (wlp58s0): state change: failed -> disconnected (reason 'none') [120 30 0] Adding insult to injury, the MAC address it lists is ... already the device's permanent MAC address. Network scanning seems to fail for the same reason, but it will pull results if I manually run scanning through iwlist.
sounds like upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=770456 Please attach a logfile with level=TRACE. See https://cgit.freedesktop.org/NetworkManager/NetworkManager/plain/contrib/fedora/rpm/NetworkManager.conf?id=c90ec2d8c8a12b44c908bf7f80b23059c29f68fa
NetworkManager-1.4.0-2.fc25 network-manager-applet-1.4.0-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-788a7edfd7
NetworkManager-1.4.0-2.fc25, network-manager-applet-1.4.0-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-788a7edfd7
1.4.0-2 is better, but not perfect. It does connect to networks eventually, but needs quite a bit of kicking and repetition to get it to work, as it still fails scanning and connections based on the MAC swapping failing. At one stage I had to restart NM entirely to get it to succeed. I'll get TRACE logs when I can.
(In reply to Daniel Stone from comment #5) > 1.4.0-2 is better, but not perfect. It does connect to networks eventually, > but needs quite a bit of kicking and repetition to get it to work, as it > still fails scanning and connections based on the MAC swapping failing. At > one stage I had to restart NM entirely to get it to succeed. > > I'll get TRACE logs when I can. first it would be interesting to see TRACE logs for 1.4.0-1. Otherwise, it cannot be said what the reason for your original failure is.
NetworkManager-1.4.0-2.fc25, network-manager-applet-1.4.0-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
seems to properly fix this, it needs more. See - https://bugzilla.redhat.com/show_bug.cgi?id=1374023#c30 - https://bugzilla.gnome.org/show_bug.cgi?id=770504#c20 This will be done with NetworkManager-1.4.0-4.fc25
NetworkManager-1.4.0-4.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca43312fe9
NetworkManager-1.4.0-4.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca43312fe9
NetworkManager-1.4.0-4.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.