Enumerations

An alias for the message bus that activated the process, if any.

Not a message bus.

The system-wide message bus.

The login session message bus.

Catch-all for unknown values

There was an error during conversion.

Some data was consumed or produced

The conversion is finished

Flushing is finished

Catch-all for unknown values

Indicates an invalid native credential type.

The native credentials type is a struct ucred.

The native credentials type is a struct cmsgcred.

The native credentials type is a struct sockpeercred. Added in 2.30.

The native credentials type is a ucred_t. Added in 2.40.

The native credentials type is a struct unpcbid. Added in 2.42.

The native credentials type is a struct xucred. Added in 2.66.

The native credentials type is a PID DWORD. Added in 2.72.

Catch-all for unknown values

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 DBusErrorNoReply is used for message reply timeouts. Warning: this is confusingly-named given that DBusErrorTimedOut 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 DBusErrorTimeout 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

Catch-all for unknown values

The byte order is big endian.

The byte order is little endian.

Catch-all for unknown values

Not a valid header field.

The object path.

The interface name.

The method or signal name.

The name of the error that occurred.

The serial number the message is a reply to.

The name the message is intended for.

Unique name of the sender of the message (filled in by the bus).

The signature of the message body.

The number of UNIX file descriptors that accompany the message.

Catch-all for unknown values

Message is of invalid type.

Method call.

Method reply.

Error reply.

Signal emission.

Catch-all for unknown values

Selects Big Endian byte order.

Selects Little Endian byte order.

Selects endianness based on host machine's architecture.

Catch-all for unknown values

Selects "LF" line endings, common on most modern UNIX platforms.

Selects "CR" line endings.

Selects "CR, LF" line ending, common on Microsoft Windows.

Automatically try to handle any line ending type.

Catch-all for unknown values

Unknown or drive doesn't support start/stop.

The stop method will physically shut down the drive and e.g. power down the port the drive is attached to.

The start/stop methods are used for connecting/disconnect to the drive over the network.

The start/stop methods will assemble/disassemble a virtual drive from several physical drives.

The start/stop methods will unlock/lock the disk (for example using the ATA SECURITY UNLOCK DEVICE command)

Catch-all for unknown values

Emblem of unknown origin

Emblem adds device-specific information

Emblem depicts live metadata, such as "readonly"

Emblem comes from a user-defined tag, e.g. set by nautilus (in the future)

Catch-all for unknown values

Attribute value is unset (empty).

Attribute value is set.

Indicates an error in setting the value.

Catch-all for unknown values

indicates an invalid or uninitialized type.

a null terminated UTF8 string.

a zero terminated string of non-zero bytes.

a boolean value.

an unsigned 4-byte/32-bit integer.

a signed 4-byte/32-bit integer.

an unsigned 8-byte/64-bit integer.

a signed 8-byte/64-bit integer.

a Object.

a Nothing terminated char **. Since 2.22

Catch-all for unknown values