Forum Discussion

jeroenb's avatar
jeroenb
New Contributor
1 year ago

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. Click...
linux
1P_David's avatar
1P_David
Icon for 1Password Team rank1Password Team
1 year ago

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

justincredible's avatar
justincredible
New Contributor
8 days ago

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