Security restrictions don't allow doing what you're trying to do.
Can't bind a socket since its address is in use (i.e. EADDRINUSE).
Asked for ADT audit data and it wasn't available.
Authentication didn't work.
A D-Bus bus address was malformed.
The connection is disconnected and you're trying to use it.
A generic error; "something went wrong" - see the error message for more.
Existing file and the operation you're using does not silently overwrite.
Missing file.
Invalid arguments passed to a method call.
A file contains invalid syntax or is otherwise broken.
A type signature is not valid.
Something went wrong reading or writing to a socket, for example.
Some limited resource is exhausted.
The match rule isn't syntactically valid.
Tried to remove or modify a match rule that didn't exist.
The bus name you referenced doesn't exist (i.e. no application owns it).
Requested operation isn't supported (like ENOSYS on UNIX).
There was not enough memory to complete an operation.
No network access (probably ENETUNREACH on a socket).
No reply to a message expecting one, usually means a timeout occurred.
Unable to connect to server (probably caused by ECONNREFUSED on a socket).
There's already an object with the requested object path.
Property you tried to set is read-only. Since 2.42
Asked for SELinux security context and it wasn't available.
The bus doesn't know how to launch a service to supply the bus name you wanted.
While starting a new process, the child exited with a status code.
While starting a new process, the child exited on a signal.
We failed to setup the config parser correctly.
While starting a new process, the exec() call failed.
While starting a new process, something went wrong.
Service file invalid (Name, User or Exec missing).
While starting a new process, the fork() call failed.
Tried to get a UNIX process ID and it wasn't available.
Permissions are incorrect on the setuid helper.
Bus name was not valid.
Service file not found in system-services directory.
We failed to setup the environment correctly.
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.
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.
Tried to get a UNIX process ID and it wasn't available.
Interface you invoked a method on isn't known by the object. Since 2.42
Method name you invoked isn't known by the object you invoked it on.
Object you invoked a method on isn't known. Since 2.42
Property you tried to access isn't known by the object. Since 2.42
Error codes for the %G_DBUS_ERROR error domain.