You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there is no Secret Service implementation available (i.e. connecting to D-Bus was successful, but there is no org.freedesktop.secrets service), the error is KeyringError::SecretServiceError(SsError::Dbus), where the name of the underlying dbus::Error is org.freedesktop.DBus.Error.ServiceUnknown.
In this situation, the keyring call should probably fail with KeyringError::NoBackendFound instead.
Failure to connect to D-Bus (because there is no session bus, and auto-starting it failed) should probably also result in KeyringError::NoBackendFound, but there doesn't appear to be a well-defined error name for that situation. Potential error names include org.freedesktop.DBus.Error.NoServer, org.freedesktop.DBus.Error.FileNotFound, or org.freedesktop.DBus.Error.NotSupported (not an exhaustive list).
The text was updated successfully, but these errors were encountered:
Finally realized that this probably belongs in keyring repo. At this moment it’s unlikely that I try to create more custom errors for dbus errors here.
When there is no Secret Service implementation available (i.e. connecting to D-Bus was successful, but there is no
org.freedesktop.secrets
service), the error isKeyringError::SecretServiceError(SsError::Dbus)
, where thename
of the underlyingdbus::Error
isorg.freedesktop.DBus.Error.ServiceUnknown
.In this situation, the keyring call should probably fail with
KeyringError::NoBackendFound
instead.Failure to connect to D-Bus (because there is no session bus, and auto-starting it failed) should probably also result in
KeyringError::NoBackendFound
, but there doesn't appear to be a well-defined error name for that situation. Potential error names includeorg.freedesktop.DBus.Error.NoServer
,org.freedesktop.DBus.Error.FileNotFound
, ororg.freedesktop.DBus.Error.NotSupported
(not an exhaustive list).The text was updated successfully, but these errors were encountered: