Enum zbus::Error [−][src]
#[non_exhaustive] pub enum Error {}Show 19 variants
InterfaceNotFound, Address(String), Io(Error), InsufficientData, InvalidField, ExcessData, Variant(VariantError), Names(NamesError), IncorrectEndian, Handshake(String), InvalidReply, MethodError(OwnedErrorName, Option<String>, Arc<Message>), MissingField, InvalidGUID, Unsupported, FDO(Box<Error>), SerdeXml(Error), NoBodySignature, UnmatchedBodySignature,
Expand description
The error type for zbus
.
The various errors that can be reported by this crate.
Variants (Non-exhaustive)
This enum is marked as non-exhaustive
Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.
Interface not found
Invalid D-Bus address.
Tuple Fields of Address
0: String
An I/O error.
Tuple Fields of Io
0: Error
Insufficient data provided to create a valid D-Bus message.
Invalid message field.
Data too large.
A zvariant error.
Tuple Fields of Variant
0: VariantError
A zbus_names error.
Tuple Fields of Names
0: NamesError
Endian signature invalid or doesn’t match expectation.
Initial handshake error.
Tuple Fields of Handshake
0: String
Unexpected or incorrect reply.
A D-Bus method error reply.
Tuple Fields of MethodError
A required field is missing in the message headers.
Invalid D-Bus GUID.
Unsupported function, or support currently lacking.
A fdo::Error
transformed into Error
.
An XML error
Tuple Fields of SerdeXml
0: Error
Unmatching/bad body signature in the message.
Trait Implementations
Performs the conversion.
Performs the conversion.