Thomas Haller d2d7a0aafc nm-online: fix wrong assertion failure during nm-online ... _return() assigns the return value @retval and asserts that currently no return-value is assigned -- in order not to overwrite a once set value. That requires, that we call _return() and exit the main-loop right away, without possibility to call _return() again. However, during client_properties_changed() we easily might receive the "notify" signal multiple times, and thus call quit_if_connected() and _return() multiple times. That would lead to a wrong assertion failure. Avoid that, by disconnecting the signal handler once we reach _return(). Fixes: f7875a42b0 (cherry picked from commit ec91f950b8)		2017-02-07 19:44:04 +01:00
..
cli	cli: add missing NULL-check	2017-01-29 14:22:45 +01:00
common	build: fix -Wold-style-declaration warnings	2017-02-06 19:42:43 +01:00
tui	all: use nm_utils_is_valid_iface_name()	2017-01-06 15:11:56 +01:00
nm-online.c	nm-online: fix wrong assertion failure during nm-online	2017-02-07 19:44:04 +01:00