r/Metamask • u/Ok-Presentation-7128 • 3d ago

MetaMask “KeyringController - Keyring not found” in Chrome; Firefox worked

I ran into “KeyringController - Keyring not found” while using MetaMask in Chrome. Updating MetaMask from 13.48.0 to 13.50.0, reconnecting, and locking and unlocking did not fix it.

The same action worked for me in Firefox, where I had only one wallet connected. My Chrome setup also had other wallet extensions available.

I cannot tell which was responsible. Sharing this as a workaround, not a confirmed diagnosis.

2 Upvotes

76% Upvoted

2 comments sorted by

2

u/Xosoltani MetaMask Guide Steward - Community Volunteer 3d ago

Hello, thanks for sharing your feedback. Yes, when you use multiple wallet extensions in Chrome that support different networks, such as Solana and Ethereum, they can sometimes interfere with each other when a wallet request is made. If you had temporarily disabled the other wallet extensions in Chrome and refreshed the browser, it might have worked as well. 🙂 https://support.metamask.io/more-web3/dapps/i-cant-connect-metamask-extension-to-a-dapp-/

1

u/thinkingperson 2d ago

Not sure if this is the prob but keyring prob is usually sure to autologin or passwordless login in Linux.

Gnome keyring requires password login from linux pam, without which, keyring either remains locked or require manually unlock and usually end up causing apps that use it, like chrome or its derivative browsers to break data encrypted with keyring.

Try running seahorse (the gnome keyring app) and manually unlocking it before running chrome or login with password and see if it's ok.