Fixing 'Sign-in is unavailable because your system keyring is not accessible'
Fix Linux sign-in keyring errors by installing/unlocking a Secret Service provider first; only recreate the GNOME Login keyring after confirming it's broken.
Vibe Typer (and other Electron apps) can show this message on Linux:
Sign-in is unavailable because your system keyring is not accessible.
In most cases, this means Vibe Typer cannot access a working Linux credential store (a Secret Service keyring).
This page starts with the same steps shown in Vibe Typer's in-app dialog. Only if those steps are already done and you can prove your keyring is broken should you use the destructive recovery section.
Before You Start
- If this started after a suspend/resume, update, or password change, try a quick log out + log in (or reboot) first.
- The last section on this page is destructive: it recreates your Login keyring, which can delete saved passwords/secrets stored there.
- If you're not sure what keyring your desktop uses (GNOME Keyring vs KWallet, etc.), stop after the checks and ask for help.
1) Start Here: Follow the In-App Keyring Setup Prompt
When Vibe Typer shows the keyring warning dialog, follow those instructions first.
Install a Secret Service provider
Arch Linux:
sudo pacman -S gnome-keyring libsecretUbuntu/Debian:
sudo apt install gnome-keyringMake sure the keyring is running and unlocked
Logging out and logging back in usually unlocks the keyring.
Hyprland/i3/wlroots sessions (especially AppImage launched from a terminal)
Some Linux sessions need an explicit password-store backend for Electron safe storage:
PASSWORD_STORE_BACKEND=gnome-libsecret ./VibeTyper.AppImage --password-store=gnome-libsecretRestart Vibe Typer
After setup, fully quit Vibe Typer and open it again.
2) If It Still Fails: Diagnose What Kind of Keyring Problem You Have
Most users with this error have a missing/locked keyring provider, not a corrupted keyring.
Check if a Secret Service provider is available on your session
This checks whether the org.freedesktop.secrets service is owned on your session bus:
dbus-send --session \
--dest=org.freedesktop.DBus \
--type=method_call \
--print-reply \
/org/freedesktop/DBus \
org.freedesktop.DBus.NameHasOwner \
string:org.freedesktop.secretsIf this returns boolean false, go back to the in-app setup steps (install/unlock the keyring, then restart Vibe Typer).
If it returns boolean true, continue.
If you use GNOME Keyring: check that gnome-keyring is running
ps aux | grep gnome-keyring-daemonYou should see a gnome-keyring-daemon process.
Advanced check: is the GNOME Login keyring collection reachable?
Only do this check if you are using gnome-keyring. (On KDE/KWallet, this login collection may not exist.)
dbus-send --session \
--dest=org.freedesktop.secrets \
--type=method_call \
--print-reply \
/org/freedesktop/secrets/collection/login \
org.freedesktop.DBus.Properties.GetAll \
string:'org.freedesktop.Secret.Collection'If the login keyring collection is broken/missing, you typically see an error like:
Error org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path "/org/freedesktop/secrets/collection/login"If you see a list of properties (like Label, Locked, Created), the login keyring exists and is reachable. In that case, your issue is probably not "corrupted login keyring"; go back to the in-app steps (unlock/restart, and use the Hyprland/i3 launch command if applicable).
3) Destructive Fix (GNOME Keyring Only): Recreate the Login Keyring
Only do this if ALL of the following are true:
- You already followed the in-app setup steps (install provider, log out/in to unlock, restart Vibe Typer).
org.freedesktop.secretsis available (the NameHasOwner check returnsboolean true).- The login collection DBus check fails with "Object does not exist" for
/org/freedesktop/secrets/collection/login.
This can delete saved passwords/secrets stored in your Login keyring.
Option A: GUI (recommended for most users)
- Open Passwords and Keys (Seahorse).
- In the left sidebar, find Login.
- Right-click it and choose Delete.
- Log out and log back in.
Your system should automatically create a fresh login keyring.
Option B: Terminal (fastest)
This deletes the login keyring file and restarts the keyring daemon.
If you want a backup first:
cp ~/.local/share/keyrings/login.keyring ~/.local/share/keyrings/login.keyring.backuprm ~/.local/share/keyrings/login.keyring && pkill -u $USER gnome-keyring-daemonThen log out and log back in (or reboot).
4) Try Vibe Typer Again
- Fully quit Vibe Typer.
- Open it again and retry sign-in.
If the error persists after recreating the login keyring, the root cause is likely different (for example: no Secret Service provider is running for your desktop session). In that case, share your distro + desktop environment and the output of the DBus check above with support.