Top |
enum | NMAgentManagerError |
#define | NM_AGENT_MANAGER_ERROR |
enum | NMConnectionError |
#define | NM_CONNECTION_ERROR |
enum | NMCryptoError |
#define | NM_CRYPTO_ERROR |
enum | NMDeviceError |
#define | NM_DEVICE_ERROR |
enum | NMManagerError |
#define | NM_MANAGER_ERROR |
enum | NMSecretAgentError |
#define | NM_SECRET_AGENT_ERROR |
enum | NMSettingsError |
#define | NM_SETTINGS_ERROR |
enum | NMVpnPluginError |
#define | NM_VPN_PLUGIN_ERROR |
GEnum ├── NMAgentManagerError ├── NMConnectionError ├── NMCryptoError ├── NMDeviceError ├── NMManagerError ├── NMSecretAgentError ├── NMSettingsError ╰── NMVpnPluginError
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
errors in the "org.freedesktop.NetworkManager.AgentManager" namespace.
unknown or unspecified error |
||
The caller does not have permission to register a secret agent, or is trying to register the same secret agent twice. |
||
The identifier is not a valid secret agent identifier. |
||
The caller tried to unregister an agent that was not registered. |
||
No secret agent returned secrets for this request |
||
The user canceled the secrets request. |
Describes errors that may result from operations involving a NMConnection or its NMSettings.
These errors may be returned directly from NMConnection and NMSetting methods, or may be returned from D-Bus operations (eg on NMClient or NMDevice), where they correspond to errors in the "org.freedesktop.NetworkManager.Settings.Connection" namespace.
unknown or unclassified error |
||
the NMConnection object did not contain the specified NMSetting object |
||
the NMConnection did not contain the requested NMSetting property |
||
an operation which requires a secret was attempted on a non-secret property |
||
the NMConnection object is missing an NMSetting which is required for its configuration. The error message will always be prefixed with "<setting-name>: ", where "<setting-name>" is the name of the setting that is missing. |
||
the NMConnection object contains an invalid or inappropriate NMSetting. The error message will always be prefixed with "<setting-name>: ", where "<setting-name>" is the name of the setting that is invalid. |
||
the NMConnection object is invalid because it is missing a required property. The error message will always be prefixed with "<setting-name>.<property-name>: ", where "<setting-name>" is the name of the setting with the missing property, and "<property-name>" is the property that is missing. |
||
the NMConnection object is invalid because a property has an invalid value. The error message will always be prefixed with "<setting-name>.<property-name>: ", where "<setting-name>" is the name of the setting with the invalid property, and "<property-name>" is the property that is invalid. |
Cryptography-related errors that can be returned from some nm-utils methods, and some NMSetting8021x operations.
Device-related errors.
These errors may be returned directly from NMDevice methods, or may be returned from D-Bus operations (where they correspond to errors in the "org.freedesktop.NetworkManager.Device" namespace).
unknown or unclassified error |
||
NetworkManager failed to create the device |
||
the specified connection is not valid |
||
the specified connection is not compatible with this device. |
||
the device does not have an active connection |
||
the requested operation is only valid on software devices. |
||
the requested operation is not allowed at this time. |
||
the "specific object" in the activation request (eg, the NMAccessPoint or NMWimaxNsp) was not found. |
||
the version id did not match. |
||
the requested operation could not be completed due to missing dependencies. |
||
invalid argument. Since: 1.16. |
Errors related to the main "network management" interface of NetworkManager. These may be returned from NMClient methods that invoke D-Bus operations on the "org.freedesktop.NetworkManager" interface, and correspond to D-Bus errors in that namespace.
unknown or unclassified error |
||
Permission denied. |
||
The requested connection is not known. |
||
The requested device is not known. |
||
The requested connection cannot be activated at this time. |
||
The request could not be completed because a required connection is not active. |
||
The connection to be activated was already active on another device. |
||
An activation request failed due to a dependency being unavailable. |
||
The manager is already in the requested sleep/wake state. |
||
The network is already enabled/disabled. |
||
Unknown log level in SetLogging |
||
Unknown log domain in SetLogging |
||
Invalid arguments for D-Bus request |
||
A plug-in was needed to complete the activation but is not available. |
NMSecretAgentError values are passed by secret agents back to NetworkManager 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
codes; instead, the secret agent manager will translate them to the
corresponding NMAgentManagerError codes.
unknown or unclassified error |
||
the caller (ie, NetworkManager) is not authorized to make this request |
||
the connection for which secrets were requested is invalid |
||
the request was canceled by the user |
||
the agent canceled the request because it was requested to do so by NetworkManager |
||
the agent cannot find any secrets for this connection |
Errors related to the settings/persistent configuration interface of NetworkManager.
These may be returned from NMClient methods that invoke D-Bus operations on the "org.freedesktop.NetworkManager.Settings" interface, and correspond to D-Bus errors in that namespace.
Returned by the VPN service plugin to indicate errors. These codes correspond to errors in the "org.freedesktop.NetworkManager.VPN.Error" namespace.
unknown or unclassified error |
||
the plugin is already starting, and another connect request was received |
||
the plugin is already connected, and another connect request was received |
||
the plugin is already stopping, and another stop request was received |
||
the plugin is already stopped, and another disconnect request was received |
||
the operation could not be performed in this state |
||
the operation could not be performed as the request contained malformed arguments, or arguments of unexpected type. Usually means that one of the VPN setting data items or secrets was not of the expected type (ie int, string, bool, etc). |
||
a child process failed to launch |
||
the operation could not be performed because the connection was invalid. Usually means that the connection's VPN setting was missing some required data item or secret. |
||
the operation could not be
performed as the plugin does not support interactive operations, such as
|