NetworkManager/clients
Francesco Giudici 3d4d1bedda nmcli: avoid calling twice "check_activated()" on "nmcli connection up"
This happens when the connection is in "activating" state and
the connection is a master one waiting for slaves: "check_activated()"
is called by the active_connection_state_cb() and device_state_cb() callbacks.

If the device has already moved to a state >= NM_DEVICE_STATE_IP_CONFIG, the
call to active_connection_state_cb() will end calling
activate_connection_info_finish(), freeing the "info" object. The subsequent
call to device_state_cb() will result in accessing the freed "info".

Just call check_activated() once after registering the
active_connection_state() and device_state_cb() callbacks.
2017-04-05 11:30:52 +02:00
..
cli nmcli: avoid calling twice "check_activated()" on "nmcli connection up" 2017-04-05 11:30:52 +02:00
common cli: fix setting of 802-1x.eap property 2017-03-30 18:34:14 +02:00
tui all: use "unsigned" instead of "unsigned int" 2017-03-14 11:26:29 +01:00
nm-online.c nm-online: fix wrong assertion failure during nm-online 2017-02-07 19:42:30 +01:00