← All troubleshooting topics

Updates

Loach’s built-in updater patches every install format in place. When it doesn’t offer to, the cause is usually an old build, a development build, release timing, or the auto-check being off.

No “Install update” button on Linux

You’re on Linux and the Updates panel only says in-app updates aren’t available for this install, with an Open releases button.

All three Linux formats - AppImage, .deb and .rpm - support in-app updates, so the panel should offer one. Two things hide it:

1. You installed v1.2.3 or earlier from a .deb or .rpm. That build’s check looked for an AppImage-only environment variable, so it reported “unsupported” on packages. Download a newer .deb / .rpm once from the releases page; in-app updates work from then on.
2. You’re running a development build (npm run tauri dev or cargo run). Package detection reads a marker the bundler writes at build time (an AppImage is recognised by the environment variable its runtime sets), which dev builds don’t have. Install a packaged build.

Note that updates are in-app only - there’s no apt or yum repository, so apt upgrade won’t pick up new versions either way.

The update asks for my password on Linux

Installing an update on a .deb / .rpm install pops a system authentication prompt.

Expected. Replacing a package-managed install means running dpkg -i / rpm -U as root, which Loach requests through pkexec (falling back to zenity or kdialog plus sudo). Going around the package manager instead would leave its database describing a version that’s no longer on disk. AppImage installs replace themselves in place and never prompt.

“You’re on the latest version” but I see a newer version on GitHub

The updater says there’s nothing new even though a newer release exists.

The updater only sees the newest published stable release. Drafts aren’t offered, and neither are pre-releases (versions with a suffix such as -beta-1 or -rc-1) - download those from GitHub.

No “Update available” notice at launch

A new version is out, but Loach never tells you when it starts.

1. The launch check is off by default. Switch on Auto-check for updates in Settings → Updates. It takes effect from the next launch, not straight away.
2. The check is deliberately quiet: there’s no notice when you’re up to date, and a check that fails (offline, release server unreachable) is only logged. Use Check for updates in the same panel to see the result or the error.
3. With an app lock, the notice waits until you unlock; it also never appears during the onboarding wizard.
4. The check runs once per launch. A notice you put off with Later - or one that was showing when Loach locked - doesn’t come back until the next launch. To install sooner, use Check for updates in Settings → Updates.

I can’t cancel an update that’s downloading

The Update available dialog won’t close, or the Updates panel has no way to stop the download.

By design. Once you pick Update now or Install update, the download can’t be stopped, and Loach restarts on its own when the update is installed - closing the dialog would only let the restart catch you by surprise. If you’re not ready, choose Later instead and install from Settings → Updates when it suits you.

Update download or signature fails

The update starts but errors out before installing, showing Update failed: and a reason.

1. Click Try again - transient network failures are common.
2. If the error mentions signature verification, the downloaded file didn’t match what the release signed - usually a corrupted or intercepted download (a proxy or antivirus rewriting it). Retry, and if it keeps failing, install from the releases page.
3. As a fallback, download the installer for your platform directly from the releases page.