These errors may be returned from operations that could cause secrets to be -requested (such as nm_client_activate_connection()), and correspond to D-Bus +requested (such as nm_client_activate_connection()), and correspond to D-Bus errors in the "org.freedesktop.NetworkManager.AgentManager" namespace.

Members

@@ -319,7 +319,7 @@ request

NM_AGENT_MANAGER_ERROR

#define NM_AGENT_MANAGER_ERROR (nm_agent_manager_error_quark ())
+#define NM_AGENT_MANAGER_ERROR (nm_agent_manager_error_quark())

@@ -420,7 +420,7 @@ the property that is invalid.

NM_CONNECTION_ERROR

#define NM_CONNECTION_ERROR nm_connection_error_quark ()
+#define NM_CONNECTION_ERROR nm_connection_error_quark()

@@ -487,7 +487,7 @@ was invalid

NM_CRYPTO_ERROR

#define NM_CRYPTO_ERROR nm_crypto_error_quark ()
+#define NM_CRYPTO_ERROR nm_crypto_error_quark()

@@ -596,7 +596,7 @@ be completed due to missing dependencies.

NM_DEVICE_ERROR

#define NM_DEVICE_ERROR nm_device_error_quark ()
+#define NM_DEVICE_ERROR nm_device_error_quark()

@@ -727,7 +727,7 @@ activation but is not available.

NM_MANAGER_ERROR

#define NM_MANAGER_ERROR (nm_manager_error_quark ())
+#define NM_MANAGER_ERROR (nm_manager_error_quark())

@@ -737,7 +737,7 @@ activation but is not available.

when they encounter problems retrieving secrets on behalf of NM. They correspond to errors in the "org.freedesktop.NetworkManager.SecretManager" namespace.

Client APIs such as nm_client_activate_connection() will not see these error +

Client APIs such as nm_client_activate_connection() will not see these error codes; instead, the secret agent manager will translate them to the corresponding NMAgentManagerError codes.

@@ -802,7 +802,7 @@ connection

NM_SECRET_AGENT_ERROR

#define NM_SECRET_AGENT_ERROR         (nm_secret_agent_error_quark ())
+#define NM_SECRET_AGENT_ERROR (nm_secret_agent_error_quark())

@@ -886,7 +886,7 @@ active settings backend

NM_SETTINGS_ERROR

#define NM_SETTINGS_ERROR (nm_settings_error_quark ())
+#define NM_SETTINGS_ERROR (nm_settings_error_quark())

@@ -992,7 +992,7 @@ performed as the plugin does not support interactive operations, such as

NM_VPN_PLUGIN_ERROR

#define NM_VPN_PLUGIN_ERROR      (nm_vpn_plugin_error_quark ())
+#define NM_VPN_PLUGIN_ERROR (nm_vpn_plugin_error_quark())

-- cgit 1.3.0-6-gf8a5 From 65f86e8f56267192d42f2b629fc6b0c99fb9cd0c Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Sun, 6 Dec 2020 21:57:59 +0100 Subject: New upstream version 1.28.0 --- docs/libnm/html/libnm-nm-errors.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/libnm/html/libnm-nm-errors.html') diff --git a/docs/libnm/html/libnm-nm-errors.html b/docs/libnm/html/libnm-nm-errors.html index d1ff13ff..759b2074 100644 --- a/docs/libnm/html/libnm-nm-errors.html +++ b/docs/libnm/html/libnm-nm-errors.html @@ -8,7 +8,7 @@ - + @@ -254,7 +254,7 @@ nm_vpn_plugin_error_quark (voidenum NMAgentManagerError Errors returned from the secret-agent manager. These errors may be returned from operations that could cause secrets to be -requested (such as nm_client_activate_connection()), and correspond to D-Bus +requested (such as nm_client_activate_connection()), and correspond to D-Bus errors in the "org.freedesktop.NetworkManager.AgentManager" namespace. Members @@ -737,7 +737,7 @@ activation but is not available. when they encounter problems retrieving secrets on behalf of NM. They correspond to errors in the "org.freedesktop.NetworkManager.SecretManager" namespace. -Client APIs such as nm_client_activate_connection() will not see these error + Client APIs such as nm_client_activate_connection() will not see these error codes; instead, the secret agent manager will translate them to the corresponding NMAgentManagerError codes. @@ -998,6 +998,6 @@ performed as the plugin does not support interactive operations, such as - Generated by GTK-Doc V1.32 + Generated by GTK-Doc V1.33.1