libnm: don't normalize connection for nm_device_get_applied_connection()

Normalizing means that we fail on invalid connections.
Which can happen when the server is newer than the libnm
version. We just want to return whatever we can. The
caller should make sense of this.

This makes libnm more accepting and thus is not going to break
existing applications. Also, nm_device_get_applied_connection()
is new API since nm-1-1.
This commit is contained in:
Thomas Haller 2016-03-17 10:37:42 +01:00
parent df405942de
commit a37c1d1e17

View file

@ -2355,7 +2355,7 @@ nm_device_get_applied_connection (NMDevice *device,
return NULL;
}
connection = nm_simple_connection_new_from_dbus (dict, error);
connection = _nm_simple_connection_new_from_dbus (dict, NM_SETTING_PARSE_FLAGS_BEST_EFFORT, error);
if (!connection)
return NULL;
@ -2397,7 +2397,7 @@ device_get_applied_connection_cb (GObject *proxy,
goto out;
}
connection = nm_simple_connection_new_from_dbus (dict, &error);
connection = _nm_simple_connection_new_from_dbus (dict, NM_SETTING_PARSE_FLAGS_BEST_EFFORT, &error);
if (!connection) {
g_simple_async_result_take_error (simple, error);
goto out;