Ubuntu dictation not pasting? Check the shortcut, transcript and target app
When dictated words do not appear, the failure can be in recording, recognition, the clipboard or text insertion. Work through those stages in order. These steps apply to Cursay’s Ubuntu GNOME/Wayland setup; they are not a promise that every Linux desktop or target app behaves the same way.
Updated · Cursay product guide
Start with one short, non-sensitive sentence
Open an ordinary text editor with an editable document. Select Local Whisper and allow its initial model download to finish. Focus the document, hold the configured shortcut, say a short sentence and release.
Use a fresh sentence you can recognize. Old clipboard text is not evidence that the latest dictation worked. Avoid testing first in a password box, remote desktop session or terminal.
If recording never starts, check the shortcut
Open Cursay Settings and use Change shortcut to request the Global Shortcuts permission again. Confirm the key combination shown by Cursay rather than assuming a default. Another app or desktop shortcut may already use the same keys.
The supported setup uses the shortcut portal on GNOME Wayland. Do not grant broad Remote Desktop access as a workaround: that is not the permission Cursay’s Ubuntu setup expects. Check microphone selection and desktop microphone access separately.
If recording works but recognition does not
Release the shortcut to end recording; pauses while holding it do not end push-to-talk. Wait for processing and check whether the current transcript becomes available.
For Local Whisper, the model must finish downloading before offline use. Processing time depends on your hardware and recording length. Start with a short sentence before testing long recordings.
If you selected a cloud or custom endpoint, check its network connection, credentials and allowance. A cloud failure does not establish a broken microphone. Use the local workflow to narrow down the problem.
If the transcript exists, test manual paste
Focus the text editor and use its Paste action. If it inserts the sentence you just dictated, recording and recognition succeeded; focus on automatic paste next.
If Paste inserts unrelated text, do not treat that as success. Check the current transcript, copy it explicitly where available, and try again. Cursay verifies clipboard delivery to avoid inserting stale text; forcing repeated pastes can hide the actual failure.
Check the supported automatic-paste setup
Cursay’s Ubuntu automatic paste uses a narrow keyboard-only input device. If the installer reported protected /dev/uinput access, run the supplied setup script from your Cursay folder and follow its administrator-authentication prompt.
Use the supplied script rather than giving every user unrestricted access to input devices. The regular dictation and clipboard workflow can still be useful without automatic paste.
./scripts/enable-autopaste.shIf the editor works but another app does not
Repeat the same short check in the target app with its text field focused. If only that app fails, recognition is unlikely to be the cause. Test its own Paste menu action before changing speech settings.
Some Ubuntu terminals use Ctrl + Shift + V instead of Ctrl + V. The published release may require manual paste there. Do not run spoken shell commands without reading the resulting text first.
If the problem persists, use the project’s GitHub page linked below to report the Ubuntu version, desktop/display session, Cursay version, which stage failed and the target app. Do not include private recordings, transcripts or credentials.
Common questions
Do I need Remote Desktop permission for Cursay on Ubuntu?
No. The documented Ubuntu setup uses the Global Shortcuts portal and a keyboard-only input device for paste.
Why does manual paste work when automatic paste does not?
Recognition and insertion are separate stages. A matching manual-paste result points to shortcut delivery, focus, permissions or target-app paste behavior rather than recognition.
Sources and next steps
This guide follows the Cursay source setup guide and published release assets. Availability may change; check those sources before installing.
Review privacy, cloud subprocessors and pricing before choosing a remote provider.
Open Cursay on GitHub