Platform
A few problems are specific to a particular operating system or IT policy, or to how Loach starts.
macOS - “Loach is damaged and can’t be opened” on first launch
macOS refuses to open the app after install, showing either “Loach is damaged and can’t be opened” or “Apple cannot verify Loach is free of malware”.
The macOS build is not Apple-notarized (ZTCS doesn’t subscribe to the Apple Developer Program), so Gatekeeper blocks it on first launch. Bypass it once and the app runs normally afterwards:
- For “Apple cannot verify…” on macOS 14 and earlier: right-click
Loach.appin Applications → Open → click Open in the prompt. - For “Apple cannot verify…” on macOS 15 and later: try to open the app once, then click Open Anyway in System Settings → Privacy & Security.
- For either message: run
xattr -cr /Applications/Loach.appin Terminal and launch normally.
Auto-updates flow through Loach’s own Ed25519-signed updater (independent of Apple), so this is a one-time install step. If a future update is blocked the same way, the same workaround applies.
macOS - Intel Macs
You’re on an Intel Mac and the .dmg won’t install or run.
The macOS build is Apple Silicon (M-series) only, and needs macOS 11 or later. Intel Macs aren’t supported. Build from source if you need to run on Intel - see Build from source.
macOS - Loach doesn’t work on an older Mac
On an older Mac, Loach installs but doesn’t work properly.
Besides macOS 11 or later, Loach needs Safari 16.4 or later. Its window runs on the system’s WebKit, which follows the installed Safari rather than the macOS version, and its Markdown rendering needs Safari 16.4’s JavaScript - so a Mac on an older Safari, such as a Big Sur or Monterey Mac still on Safari 14 or 15, has to update Safari first.
macOS - closing the window doesn’t quit Loach
You closed Loach’s window, but it’s still in the Dock and the menu bar.
Like other Mac apps, Loach keeps running when you close its window (the red button or ⌘ + W), and a reply in progress carries on. Click its Dock icon, or Show Loach in its menu-bar icon, to bring the window back; quit with ⌘ + Q or Quit in the menu-bar icon. With an app lock set, closing the window also locks Loach. The window uses the system’s own buttons on macOS, which hide in full screen as in other apps.
macOS - Ctrl shortcuts don’t work
On a Mac, Ctrl + K, Ctrl + N and the other shortcuts in these docs do nothing, or move the text cursor instead.
On macOS, Loach’s shortcuts use ⌘ only - press ⌘ wherever these docs say Ctrl. Ctrl is left to the text field, where macOS gives it meanings of its own: Ctrl + K deletes to the end of the line, and Ctrl + N and Ctrl + F move the cursor. See Keyboard shortcuts.
Linux - the app won’t start on an older distribution
Launching Loach fails with an error such as version `GLIBC_2.35' not found.
Loach’s Linux packages are built against glibc 2.35, so Ubuntu 22.04 and Debian 12 are the oldest supported distributions; anything with an older glibc can’t run the pre-built .deb, .rpm or .AppImage. Upgrade the distribution, or build from source on the machine itself.
“Loach failed to start”
Launching Loach shows a Loach failed to start dialog, and the app closes when you dismiss it.
Loach couldn’t set itself up, and the dialog says why, with the details below: its app-data folder couldn’t be found or created, the database couldn’t be opened or updated, or its HTTP client couldn’t start (TLS or root certificates may be missing). Check that the app-data folder is writable and the disk isn’t full. If it keeps happening, file an issue with the details from the dialog.
Windows - saving a key or the app lock fails on a managed machine
Saving keys or app-lock credentials fails on a managed Windows machine with a platform or storage error.
Some corporate group policies block apps from writing to Credential Manager. Loach cannot store secrets without it. Ask your IT admin to allow Credential Manager writes for the Loach process, or use a personal machine.
On Linux, the equivalent problem is a missing Secret Service - see Key won’t save on Linux.
Launching Loach again doesn’t open a second window
You start Loach while it’s already running, and no second window appears.
Loach runs as a single instance: launching it again - from the Start menu, a desktop file or a double click - brings the running window forward instead, out of the tray too, rather than starting a second copy over the same database.