randomnetcat
21 days agoNew Contributor
Linux client fails to save 2FA token when gnome-keyring is running
I am running NixOS using Gnome, and I have enabled gnome-keyring (and I have verified that gnome-keyring is in fact running and that the org.gnome.keyring bus is bound using busctl). 1Password consistently fails to save its 2FA token.
The log file contains this line:
WARN 2025-04-14T07:45:16.372+00:00 runtime-worker(ThreadId(2)) [1P:op-b5-client/src/internal/unauthorized_session.rs:1054] Failed to save an account's 2FA token with an error of SystemKeyringError(LinuxError(DBus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.ServiceUnknown")))), Some("The name org.kde.kwalletd5 was not provided by any .service files"), Msg { type: Error, sender: UniqueName(Str(Borrowed("org.freedesktop.DBus"))), reply-serial: 2, body: Signature("s") })))). 2FA will only be valid for this unlock session!
This suggests that 1Password is attempting to use KDE's kwallet as a storage backend rather than gnome-keyring.
How does 1Password determine what keyring backend to use? Is there a way to override this choice?