Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
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.
4 Replies
I have this exact same problem, also using Arch. Without a keyring daemon I get the error above, somewhat as expected. However, with the daemon (gnome-keyring) running I also get this error:
ERROR 2026-01-13T23:29:58.991+00:00 runtime-worker(ThreadId(16)) [1P:data/op-syncer/src/system_vault.rs:29] Error creating system vault for account (xxxx): FetchDataError(FetchError(<unknown reason>, code: HttpStatus(400), Session ID: Some(Session ID: XQ52ORWGXZFXBAJH3MY23F3W4E)))
Had the same problem, it was missing to start polkit-gnome-authentication on `/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1`
1P_David1Password Team
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
I'm having the same issue on Fedora Workstation 43 (GNOME). The cause of mine is clear. I deleted my keyring as part of a fix for an unrelated issue. I saw that 1Password has a 2FA item in the keyring and it's not there anymore. So I ran `journalctl -f` as I authenticated to see what's going on. I get the same output at OP.
I have a default keyring installed and another program was able to add an item.
I see that my new keyring is called "Default_keyring.keyring" when it was "Login.keyring" when I installed the system. I renamed it manually by going to `~/.local/share/keyrings` and then `mv Default_keyring.keyring Login.keyring` and logged out and back in. Then I logged into 1Password, entered my 2FA and 1Password was able to store the entry in my keyring. I don't know which part of these steps is necessary, but it solved my problem, so I'm sharing it here for others
