Bug storing Two Factor Token on Arch Linux
When starting 1Password and after unlocking I get prompted for the Two Factor token, which is fine. However, upon entering the code, I get an error message showing 1P could not store the token. Clicking 'read more' does not work. After running 1P from the terminal, I was able to fetch the following:
INFO 2024-12-26T10:24:54.731+00:00 runtime-worker(ThreadId(30)) [1P:op-b5-client/src/internal/unauthorized_session.rs:1265] Verifying device secret (MFA) with server... INFO 2024-12-26T10:24:54.896+00:00 runtime-worker(ThreadId(28)) [1P:op-b5-client/src/internal/unauthorized_session.rs:926] Device secret was verified WARN 2024-12-26T10:24:54.903+00:00 runtime-worker(ThreadId(28)) [1P:op-b5-client/src/internal/unauthorized_session.rs:939] 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 is not activatable"), 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! INFO 2024-12-26T10:24:54.905+00:00 runtime-worker(ThreadId(30)) [1P:data/op-add-account/src/first_sync.rs:522] starting initial account sync
Can you help me out?
Small update: meanwhile I also installed polkit
along with lxsession
which provides an agent.
Comments
-
Hi @jereonb, thanks for reaching out!
I'm sorry that you're experiencing trouble storing your two-factor token. In order to store the token, you'll need to have installed a keyring if your environment doesn't come with it, and you'll need to ensure that the keyring daemon is running. Can you confirm if that's already been done on your device?
I look forward to hearing from you!
-David
0