Troubleshooting
Common Sotto problems and their fixes: no model, the shortcut not firing, nothing being pasted, the overlay on the wrong monitor, slow transcription.
“No speech model installed”
Open Settings → Model and download one. Nothing works without it.
Large v3 Turbo on a discrete GPU, Small on integrated graphics or CPU. See Speech models.
The shortcut does not do anything
Sotto asks your desktop for the shortcut through the GlobalShortcuts portal, which Plasma 5.25 and later provide. Some desktops do not have it.
Fix: disable the shortcut in Settings → Shortcut, then bind sotto --toggle in your
desktop’s own shortcut settings — System Settings → Shortcuts → Custom on KDE, or your
compositor’s config file elsewhere. It behaves identically.
Also check the binding has not been claimed by something else, in your desktop’s shortcut list.
Nothing gets pasted into the application
In order:
- Install
wl-clipboard. Nothing clipboard-based works without it. - Set up ydotool, or accept the one-time RemoteDesktop permission prompt when it appears. One of the two is needed to synthesise the paste keystroke.
- If the target is a terminal, the default
CtrlVwill not paste — terminals useCtrlShiftV. Switch to Type it or Clipboard only in Settings → Output.
In the worst case, the text is always left on the clipboard, so it is never lost.
The overlay appears on the wrong monitor
With LayerShellQt installed and the screen setting on auto, your compositor places the overlay on the active output — and it is re-evaluated every time it appears.
Without LayerShellQt, the fallback window uses the screen under the mouse pointer instead.
Fix: install layer-shell-qt, or pin a specific monitor in Settings → Appearance.
Transcription is slow
Look at the backend named at the bottom of the Settings window.
- It says
cpu— that is the problem. Rebuild with-DSOTTO_GPU=vulkan(orhipfor ROCm,cudafor NVIDIA). See Installing. - It names a GPU backend — try a smaller model. Large v3 is significantly heavier than Large v3 Turbo for a modest accuracy gain.
ROCm will not start, or produces garbage
If your GPU is not officially supported by ROCm, set HSA_OVERRIDE_GFX_VERSION before running —
10.3.0 covers many RDNA2 cards.
If that does not help, build with -DSOTTO_GPU=vulkan instead. On AMD, Vulkan is often within a
few percent of ROCm for this workload and far less sensitive to driver versions.
Accuracy is poor
In rough order of impact:
- The microphone. A headset beats a laptop microphone across a room by more than any model upgrade will.
- A bigger model. Small → Large v3 Turbo is a real step up.
- Pin the language in Settings → Model instead of leaving it on auto. Detection can guess wrong on a short first utterance.
- Speak in complete sentences. Whisper uses sentence context; fragments give it nothing to work with.
Random line breaks appear in my text
You are probably saying a phrase that contains “new line” or “new paragraph” — “a new line of products” is the classic. Turn voice commands off in Settings → Formatting and use pauses for paragraphing instead.
If paragraphs are breaking where you did not pause deliberately, raise the pause threshold in the same place.
My words get cut off at the start
Sotto keeps a short rolling buffer specifically so the first words are not clipped, so this is unusual. Check that the right input device is selected in Settings → Audio, and that it is not being brought up by a noise-suppression layer that gates the first fraction of a second.
A second sotto command does nothing visible
That is correct behaviour. A running Sotto owns its session-bus name, so a second invocation forwards its command to the first and exits — it does not start a second process. See Notepad and CLI.
Still stuck?
Note which desktop and compositor you are on, what the Settings window reports as the backend, and which model you have installed — those three answer most questions before they are asked.