On Fri, 10 Jan 2025, K0LNY ?? wrote:
Also, it might help after installing espeak-ng, to run spd-conf and making
sure espeak-ng is selected.
Also, install python3-speechd
spdconf and python3-speechd both relate to speech dispatcher.
espeakup does not use speech dispatcher so will make no difference.
Also, espeakup is not written in Python.
It is possible to use speakup via speech dispatcher, using the speechd-up
package, but this puts more layers between speakup and the audio output
which is probably not great for latency. Even the package description
recommends using more direct methods instead if you can.
To comment on the original question, there is an issue in Bookworm with
espeakup under certain circumstances. This has been discussed at length
on this list and I recently tried to reactivate the discussion to make
sure that it gets fixed.
However, I doubt that this is what's happening here.
Certainly all accounts I've seen of this issue, including my own
experience, is that espeakup works fine for awhile and then suddenly dies.
this can take awhile to happen and seems to be related in part to what the
user is doing.
If you want to be sure that this isn't the issue, running the following
command as root:
killall -9 espeakup
should resolve it.
If you want to make sure that espeak itself is working, you can run
something like:
espeak-ng hello
However, this will require the espeak-ng package to be installed, not just
libespeak-ng1. The espeak-ng package is not a dependency of espeakup so
you may not have it installed.
Apart from testing that espeak is working, the usefullness of having it is
that you can run commands in the shell and pipe the output to espeak-ng
and have it speak it, which can be very useful when your screen reader is
not speaking.
HTH,
Geoff.
