GDBusError

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

There was not enough memory to complete an operation.

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

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

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

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

A D-Bus bus address was malformed.

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

Some limited resource is exhausted.

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

Authentication didn't work.

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

Certain timeout errors, possibly ETIMEDOUT on a socket. Note that gio.types.DBusError.NoReply is used for message reply timeouts. Warning: this is confusingly-named given that gio.types.DBusError.TimedOut also exists. We can't fix it for compatibility reasons so just be careful.

No network access (probably ENETUNREACH on a socket).

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

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

Invalid arguments passed to a method call.

Missing file.

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

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

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

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

The match rule isn't syntactically valid.

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

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

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

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

While starting a new process, something went wrong.

We failed to setup the environment correctly.

We failed to setup the config parser correctly.

Bus name was not valid.

Service file not found in system-services directory.

Permissions are incorrect on the setuid helper.

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

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

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

A type signature is not valid.

A file contains invalid syntax or is otherwise broken.

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

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

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

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

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

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

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