summaryrefslogtreecommitdiff
path: root/libnm
diff options
context:
space:
mode:
authorDan Winship <danw@gnome.org>2014-10-16 18:00:54 -0400
committerDan Winship <danw@gnome.org>2014-10-19 09:27:47 -0400
commit4779d96685b3e2c295218088db8a3999450da39b (patch)
tree58539c313b892c755bf24e7432c69f55475dc38d /libnm
parentd78ea27d36a0ba3039c6c1b1b94e4ae784afa4ab (diff)
downloadNetworkManager-4779d96685b3e2c295218088db8a3999450da39b.tar.gz
core: lie about NMActiveConnection:state in new connections
NMActiveConnections start out in state "unknown", but then quickly switch to "activating". Unfortunately, it's sometimes possible for this to be externally visible. Fix this by lying and saying that state is "activating" during the initial "unknown" stage (though not if the state changes to "unknown" later on). (Actually changing the initial state to "activating" breaks things because some code depends on there being a transition into the "activating" state.)
Diffstat (limited to 'libnm')
0 files changed, 0 insertions, 0 deletions