Beniamino Galvani 3af068a5de cli: wait for changed signal after updating a connection ... In editor_menu_main(), after saving a connection we wait that the Update2() D-Bus call returns and then we copy the NMRemoteConnection instance over to @connection. This assumes that when Update2() returns the remote connection instance is already updated with new settings. Indeed, on server side the NMSettingsConnection first emits the "Updated" signal and then returns to Update2(). However, the Updated signal doesn't include the new setting values and so libnm has to fire an asynchronous nmdbus_settings_connection_call_get_setting() to fetch the new settings, which terminates after the Update2(). So, to be sure that the remote connection got updated we have also to listen to the connection-changed signal, which is always emitted after an update. https://bugzilla.redhat.com/show_bug.cgi?id=1546805 (cherry picked from commit a370faeb59)		2018-11-20 15:27:36 +01:00
..
cli	cli: wait for changed signal after updating a connection	2018-11-20 15:27:36 +01:00
common	dhcp: add "ipv4.dhcp-client-id=duid" setting	2018-11-14 14:18:06 +01:00
tests	cli/tests: fix output on failure	2018-11-02 17:07:41 +01:00
tui	cli: fix reading "vpn.secrets.*" from passwd-file	2018-09-14 15:17:53 +02:00
meson.build	build: create "config-extra.h" header instead of passing directory variables via CFLAGS	2018-07-17 17:46:39 +02:00
nm-online.c	nm-online: print "[started|start-pending|failure]" for --wait-for-startup	2018-06-30 10:59:08 +02:00