Post History

Although you have left a post saying it is solved, I think it's not uncommon for this kind of problem to show up. I think it can happen due to misconfiguration of either NM or the network drivers/hardware. It would be more useful to have a general troubleshooting question for dealing with NM timeouts.

In your case, I suspect that some changes were made to either NM config or system networking configs by the update. Since normally updates do not change user configs, probably what happened is that the upstream changed defaults you were not aware of and pulled the rug out of you, so to speak.

What I would do is:

* Look for a detailed log from the package manager about what files exactly were modified. Figure out what version of each package I used to have and find the old version of those files. Check what actually changed and see if that reveals anything obvious.
* Downgrade the NM package to what it was before. If a change in NM caused this, it should start working again. If not, we know the problem is outside NM.
* Examine detailed log output from NM regarding what it is doing. There may be a `--debug` or `--verbose` option that can be enabled for this.
* Try purging NM, including configs, and installing from scratch and following most recent instructions.