Hi All, One area I’m curious about is if this might actually be a flaw in the way Espeak/Espeakup handles Alsa. Espeak itself hasn’t been updated i quit a while, and I wonder if it might be showing its age. I guess those with coding skill can look into this better than I. > On Aug 9, 2016, at 3:58 AM, Chris Brannon <chris@xxxxxxxxxxxxxxxx> wrote: > > Kyle <kyle4jesus@xxxxxxxxx> writes: > >> I was ready to release TalkingArch this month, just a little >> late. Looks like I may need to hold off until next month. Is this a >> mostly correct assessment, or is my build from Saturday OK to continue >> the testing and sign-off process? Thanks for the heads-up. > > I don't know which package your Saturday build contains. > When did 1.1.2 hit [extra]? It was probably sometime close to then. > If you've got alsa-lib 1.1.1 or older, you should be good to go. > > So I've spent the best part of 3 hours tonight looking at the espeak > source. I'm reasonably convinced there's a race condition in the audio > output code, even though it looks like plenty of care was taken to > guarantee that this couldn't happen. Or maybe I'm seeing > things that aren't really there, and there's no race after all. > Sometimes I feel like the most phony of amateurs. > Anyway what I think happened is that a change to the alsa library has > done something to trigger a race condition that has been around for a > long time. > > -- Chris > _______________________________________________ > 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
