Lubomir Rintel 7d80a17631 cli: Finish waiting for the device activation when it disconnects ... The device status alone is uninteresting as its changes can be due to deactivation of previously active connection. We should monitor the active connection changes instead of device state changes. However the device state changes is still interesting, as it contains the reason for the change, let's just ignore them while the connection is activating. Lastly, we need to handle failures as well. It should be noted that it's not sufficient to deal with NM_DEVICE_STATE_FAILED as the device will quickly draverse to NM_DEVICE_STATE_DISCONNECTED. This happens in case of a failure due to NM_DEVICE_STATE_REASON_NO_SECRETS as soon as the server makes sure it won't reconnect automatically.		2014-11-14 16:46:40 -06:00
..
cli	cli: Finish waiting for the device activation when it disconnects	2014-11-14 16:46:40 -06:00
common	clients: only handle secret requests for connection being explicitly activated	2014-11-12 13:41:49 +01:00
tui	all: consistently include config.h	2014-11-13 17:18:42 -05:00
Makefile.am	libnm: port to GDBus	2014-09-18 11:51:09 -04:00
nm-online.c	all: consistently include config.h	2014-11-13 17:18:42 -05:00