Comment 63 for bug 291062

When this symptom has happened to me, the following command instantly fixes it:
    nmcli nm wakeup

The circumstances seem to be that NM sets NetworkingEnabled to false in the /var/lib/NetworkManager/NetworkManager.state file but the situation can arise where NM cannot reset it.

My guess is that this flag is set at suspend time (and of course at 'nmcli nm sleep' time as well). Further, I guess that NM expects a 'suspend' to be followed by a 'resume', which should reset this flag to be NetworkingEnabled=true. But if the latter fails, as it stands manual intervention is reqired.

The failure can occur in at least these two ways: the hardware's suspend function is broken and a power-on reboot is required, and the battery discharges and a power-on reboot is required. The NetworkingEnabled=false flag remains set in these cases, and manual intervention is required. But a naïve user is at a complete loss what to do. Even sophisticated users, e.g., helpers on the #fedora channel of freenode, are at a loss, as I've seen. NM should perhaps set the flag to true when freshly started?

What are the exact and complete semantics of this NetworkingEnabled=false flag?

Is there a valid case where a freshly started NetworkManager service can expect NetworkingEnabled=false to be the proper setting? If there is, could a freshly started NM pop up a graphic window asking the user if enabling was okay?