Gio.DBusError
Description: Reference for Gio.DBusError

### Enumeration

# GioDBusError

since: 2.26

#### Declaration

    error-domain Gio.DBusError

#### Description [src]

Error codes for the `G_DBUS_ERROR` error domain.

Available since: 2.26

#### Members

`G_DBUS_ERROR_FAILED`

  A generic error; “something went wrong” - see the error message for more.

  - Value: `0`
  - Available since: 2.26
`G_DBUS_ERROR_NO_MEMORY`

  There was not enough memory to complete an operation.

  - Value: `1`
  - Available since: 2.26
`G_DBUS_ERROR_SERVICE_UNKNOWN`

  The bus doesn’t know how to launch a service to supply the bus name you wanted.

  - Value: `2`
  - Available since: 2.26
`G_DBUS_ERROR_NAME_HAS_NO_OWNER`

  The bus name you referenced doesn’t exist (i.e. no application owns it).

  - Value: `3`
  - Available since: 2.26
`G_DBUS_ERROR_NO_REPLY`

  No reply to a message expecting one, usually means a timeout occurred.

  - Value: `4`
  - Available since: 2.26
`G_DBUS_ERROR_IO_ERROR`

  Something went wrong reading or writing to a socket, for example.

  - Value: `5`
  - Available since: 2.26
`G_DBUS_ERROR_BAD_ADDRESS`

  A D-Bus bus address was malformed.

  - Value: `6`
  - Available since: 2.26
`G_DBUS_ERROR_NOT_SUPPORTED`

  Requested operation isn’t supported (like ENOSYS on UNIX).

  - Value: `7`
  - Available since: 2.26
`G_DBUS_ERROR_LIMITS_EXCEEDED`

  Some limited resource is exhausted.

  - Value: `8`
  - Available since: 2.26
`G_DBUS_ERROR_ACCESS_DENIED`

  Security restrictions don’t allow doing what you’re trying to do.

  - Value: `9`
  - Available since: 2.26
`G_DBUS_ERROR_AUTH_FAILED`

  Authentication didn’t work.

  - Value: `10`
  - Available since: 2.26
`G_DBUS_ERROR_NO_SERVER`

  Unable to connect to server (probably caused by ECONNREFUSED on a socket).

  - Value: `11`
  - Available since: 2.26
`G_DBUS_ERROR_TIMEOUT`

  Certain timeout errors, possibly ETIMEDOUT on a socket. Note that `G_DBUS_ERROR_NO_REPLY` is used for message reply timeouts. Warning: this is confusingly-named given that `G_DBUS_ERROR_TIMED_OUT` also exists. We can’t fix it for compatibility reasons so just be careful.

  - Value: `12`
  - Available since: 2.26
`G_DBUS_ERROR_NO_NETWORK`

  No network access (probably ENETUNREACH on a socket).

  - Value: `13`
  - Available since: 2.26
`G_DBUS_ERROR_ADDRESS_IN_USE`

  Can’t bind a socket since its address is in use (i.e. EADDRINUSE).

  - Value: `14`
  - Available since: 2.26
`G_DBUS_ERROR_DISCONNECTED`

  The connection is disconnected and you’re trying to use it.

  - Value: `15`
  - Available since: 2.26
`G_DBUS_ERROR_INVALID_ARGS`

  Invalid arguments passed to a method call.

  - Value: `16`
  - Available since: 2.26
`G_DBUS_ERROR_FILE_NOT_FOUND`

  Missing file.

  - Value: `17`
  - Available since: 2.26
`G_DBUS_ERROR_FILE_EXISTS`

  Existing file and the operation you’re using does not silently overwrite.

  - Value: `18`
  - Available since: 2.26
`G_DBUS_ERROR_UNKNOWN_METHOD`

  Method name you invoked isn’t known by the object you invoked it on.

  - Value: `19`
  - Available since: 2.26
`G_DBUS_ERROR_TIMED_OUT`

  Certain timeout errors, e.g. while starting a service. Warning: this is confusingly-named given that `G_DBUS_ERROR_TIMEOUT` also exists. We can’t fix it for compatibility reasons so just be careful.

  - Value: `20`
  - Available since: 2.26
`G_DBUS_ERROR_MATCH_RULE_NOT_FOUND`

  Tried to remove or modify a match rule that didn’t exist.

  - Value: `21`
  - Available since: 2.26
`G_DBUS_ERROR_MATCH_RULE_INVALID`

  The match rule isn’t syntactically valid.

  - Value: `22`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_EXEC_FAILED`

  While starting a new process, the `exec()` call failed.

  - Value: `23`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_FORK_FAILED`

  While starting a new process, the `fork()` call failed.

  - Value: `24`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_CHILD_EXITED`

  While starting a new process, the child exited with a status code.

  - Value: `25`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_CHILD_SIGNALED`

  While starting a new process, the child exited on a signal.

  - Value: `26`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_FAILED`

  While starting a new process, something went wrong.

  - Value: `27`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_SETUP_FAILED`

  We failed to setup the environment correctly.

  - Value: `28`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_CONFIG_INVALID`

  We failed to setup the config parser correctly.

  - Value: `29`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_SERVICE_INVALID`

  Bus name was not valid.

  - Value: `30`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_SERVICE_NOT_FOUND`

  Service file not found in system-services directory.

  - Value: `31`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_PERMISSIONS_INVALID`

  Permissions are incorrect on the setuid helper.

  - Value: `32`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_FILE_INVALID`

  Service file invalid (Name, User or Exec missing).

  - Value: `33`
  - Available since: 2.26
`G_DBUS_ERROR_SPAWN_NO_MEMORY`

  Tried to get a UNIX process ID and it wasn’t available.

  - Value: `34`
  - Available since: 2.26
`G_DBUS_ERROR_UNIX_PROCESS_ID_UNKNOWN`

  Tried to get a UNIX process ID and it wasn’t available.

  - Value: `35`
  - Available since: 2.26
`G_DBUS_ERROR_INVALID_SIGNATURE`

  A type signature is not valid.

  - Value: `36`
  - Available since: 2.26
`G_DBUS_ERROR_INVALID_FILE_CONTENT`

  A file contains invalid syntax or is otherwise broken.

  - Value: `37`
  - Available since: 2.26
`G_DBUS_ERROR_SELINUX_SECURITY_CONTEXT_UNKNOWN`

  Asked for SELinux security context and it wasn’t available.

  - Value: `38`
  - Available since: 2.26
`G_DBUS_ERROR_ADT_AUDIT_DATA_UNKNOWN`

  Asked for ADT audit data and it wasn’t available.

  - Value: `39`
  - Available since: 2.26
`G_DBUS_ERROR_OBJECT_PATH_IN_USE`

  There’s already an object with the requested object path.

  - Value: `40`
  - Available since: 2.26
`G_DBUS_ERROR_UNKNOWN_OBJECT`

  Object you invoked a method on isn’t known. Since 2.42.

  - Value: `41`
  - Available since: 2.26
`G_DBUS_ERROR_UNKNOWN_INTERFACE`

  Interface you invoked a method on isn’t known by the object. Since 2.42.

  - Value: `42`
  - Available since: 2.26
`G_DBUS_ERROR_UNKNOWN_PROPERTY`

  Property you tried to access isn’t known by the object. Since 2.42.

  - Value: `43`
  - Available since: 2.26
`G_DBUS_ERROR_PROPERTY_READ_ONLY`

  Property you tried to set is read-only. Since 2.42.

  - Value: `44`
  - Available since: 2.26

#### Type functions

###### g_dbus_error_encode_gerror

Creates a D-Bus error name to use for `error`. If `error` matches a registered error (cf. g_dbus_error_register_error()), the corresponding D-Bus error name will be returned.

since: 2.26

###### g_dbus_error_get_remote_error

Gets the D-Bus error name used for `error`, if any.

since: 2.26

###### g_dbus_error_is_remote_error

Checks if `error` represents an error received via D-Bus from a remote peer. If so, use `g_dbus_error_get_remote_error()` to get the name of the error.

since: 2.26

###### g_dbus_error_new_for_dbus_error

Creates a `GError` based on the contents of `dbus_error_name` and `dbus_error_message`.

since: 2.26

###### g_dbus_error_quark

No description available.

###### g_dbus_error_register_error

Creates an association to map between `dbus_error_name` and `GErrors` specified by `error_domain` and `error_code`.

since: 2.26

###### g_dbus_error_register_error_domain

Helper function for associating a `GError` error domain with D-Bus error names.

since: 2.26

###### g_dbus_error_set_dbus_error

Does nothing if `error` is `NULL`. Otherwise sets `*error` to a new `GError` created with `g_dbus_error_new_for_dbus_error()` with `dbus_error_message` prepend with `format` (unless `NULL`).

since: 2.26

###### g_dbus_error_set_dbus_error_valist

Like `g_dbus_error_set_dbus_error()` but intended for language bindings.

since: 2.26

###### g_dbus_error_strip_remote_error

Looks for extra information in the error message used to recover the D-Bus error name and strips it if found. If stripped, the message field in `error` will correspond exactly to what was received on the wire.

since: 2.26

###### g_dbus_error_unregister_error

Destroys an association previously set up with g_dbus_error_register_error().

since: 2.26