Fixing 'Sign-in is unavailable because your system keyring is not accessible'

Current Vibe Typer builds can sign in without a keyring. The session is stored in a user-only file instead.

If you keep getting signed out

A keyring that works on some launches and not others used to cost you the session every time it went away again, so you had to request a new emailed code. Newer builds handle this differently.

Once the keyring fails, Vibe Typer saves the session to ~/.config/vibe-typer/supabase-session-v1.json, a file only your account can read. You may have to sign in once more for that to happen. From then on that machine keeps using the file, even on launches where the keyring works again. That is deliberate, and it is why the repeated sign-ins stop.

The trade is that the session sits on disk unencrypted, protected by file permissions alone. If you later fix your keyring and want the session encrypted again, delete both session files and sign in once more:

rm -f ~/.config/vibe-typer/supabase-session-v1.json ~/.config/vibe-typer/supabase-session-v1.dat

Delete both, not just one. Signing in after that stores the session through the keyring again.

Older builds, and a few failure cases, still show this message:

Sign-in is unavailable because your system keyring is not accessible.

That means Vibe Typer could not 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 with 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 libsecret

Ubuntu/Debian:

sudo apt install gnome-keyring

Make sure the keyring is running and unlocked

Logging out and logging back in usually unlocks the keyring.

That does not help if your machine logs in automatically. Your desktop unlocks the Login keyring with the password you type at the login screen, and automatic login never asks for one, so the keyring stays locked for the whole session. This is a common setup on Zorin, Ubuntu and other GNOME desktops used by one person.

Two ways out. Turn automatic login off in your system settings, or give the Login keyring an empty password so it unlocks on its own. For the second, open Passwords and Keys (seahorse), right-click the Login keyring, choose Change Password, enter your current password, and leave the new one blank. Anything stored in that keyring is then readable by any program running as you.

Hyprland/i3/wlroots sessions (especially AppImage launched from a terminal)

Some Linux sessions need an explicit password-store backend for Electron safe storage:

./VibeTyper.AppImage --password-store=gnome-libsecret

Restart Vibe Typer

After setup, fully quit Vibe Typer and open it again.

2) If it still fails, work out which 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.secrets

If 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-daemon

You 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 such as Label, Locked and Created, the login keyring exists and is reachable. In that case your login keyring is probably not corrupted. Go back to the in-app steps: unlock, restart, and use the Hyprland/i3 launch command if it applies.

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.secrets is available (the NameHasOwner check returns boolean 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: the GUI, best for most people

1. Open Passwords and Keys (Seahorse).
2. In the left sidebar, find Login.
3. Right-click it and choose Delete.
4. Log out and log back in.

Your system should automatically create a fresh login keyring.

Option B: the 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.backup

rm ~/.local/share/keyrings/login.keyring && pkill -u $USER gnome-keyring-daemon

Then log out and log back in (or reboot).

Recreating the keyring changes the key Vibe Typer encrypted your session with, so it signs you out once. Sign in again and the new session is stored under the new keyring.

4) Try Vibe Typer again

1. Fully quit Vibe Typer.
2. Open it again and retry sign-in.

If the error persists after recreating the login keyring, the root cause is probably something else, such as no Secret Service provider running for your desktop session. In that case, share your distro + desktop environment and the output of the DBus check above with support.