Sign-in stuck or "on hold": when this computer cannot save your account

You entered the right username and password, but the app says your sign-in is on hold, or it shows an error about saving your account on this computer. This article explains what that message means and how to clear it. The short version: the problem is this machine, not your account.

What "on hold" means

When you sign in, Booked Solid OS saves your sign-in in your computer's secure storage so you stay signed in next time. If the computer cannot store it safely, the app puts the sign-in on hold and shows a note like This computer cannot store your account safely yet. Your password was correct and your account is fine. The app just could not write the sign-in to this machine.

Fix the machine-side causes first

1. Check disk space. A full disk stops the app from saving anything. Free up some space, then sign in again.
2. Check for read-only folders. If the app's data folder is read-only (this can happen after restoring from a backup or moving files between computers), the save fails. Make sure the folder is writable, then retry.
3. Check your antivirus. Some antivirus tools temporarily lock the app's files while scanning them. If that happens at the exact moment you sign in, the save fails even though everything else worked. Wait a minute and try again, or add the app to your antivirus exceptions.

Why the app backs out instead of half-signing you in

Here is the part that can look strange: the server can accept your sign-in, and the app can still show an error. That happens when the server says yes but the local save fails right after (for example, antivirus locking the app's files). Rather than leave you half-signed-in with a sign-in it could not keep, the app rolls the whole thing back and shows a clear on-this-computer error. Signing in again once the cause is fixed takes seconds and loses nothing.

On Linux without a keyring

Some Linux desktops have no OS keyring. There, the app shows a one-time notice: This computer has no secure keyring, so your sign-in is saved in a less protected way. Installing a keyring (gnome-keyring) enables full protection. The app still works. Installing gnome-keyring restores full protection. Only the sign-in uses this fallback, never your API keys.

If it keeps happening

Restart the app and sign in once more. If the error comes back, the app has already logged what went wrong, so the help desk can see the cause. Mention the exact message you saw when you write in.

Still stuck? Email bookedsolid@kivimedia.freshdesk.com and a person will help.