Dear Chuck, You missed some discussion on this a few weeks ago. To sum up, it’s a Portaudio bug which has been noticed thanks to an Alsa upgrade, and there is a temporary workaround. All you need to do is edit “espeakup.service,” or create a drop-in snippet. In the [Service] section, put the line Environment=LIBASOUND_THREAD_SAFE=0 Case is important here, and the way I did it was to just do “sudo systemctl edit espeakup.service.” I hope this helps. Best, Zack. > On Aug 31, 2016, at 12:01 PM, Chuck Hallenbeck <chuckhallenbeck@xxxxxxxxx> wrote: > > Hello everyone, > > I've been away for some time, but have just resubscribed. > I currently use ArchLinux on a Dell Optiplex 780, refurbished, from Amazon. > Also still stubbornly using only command line interface, > just can't warm up to a GUI. > > I'm Currently having an issue involving random failures of speech, > and am able to restore speech by issuing two systemctl commands, > one to stop espeakup.service, and the next to start it again. > How can I get further information to narrow the problem down to > espeakup, or speakup, or espeak? Recovery from the failures is reliable, > but I'd rather find and fix the cause. > > Chuck > > > -- > Willoughby Ohio > Temperature 75�F > Conditions Light Rain > The Moon is New > _______________________________________________ > Speakup mailing list > Speakup@xxxxxxxxxxxxxxxxx > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup _______________________________________________ Speakup mailing list Speakup@xxxxxxxxxxxxxxxxx http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
