From: Chris Brannon <chris@the-brannons.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: you really do not want to upgrade to alsa-lib 1.1.2
Date: Tue, 09 Aug 2016 03:58:20 -0700 [thread overview]
Message-ID: <87wpjqcipf.fsf@mushroom.localdomain> (raw)
In-Reply-To: <57A9AA48.4080608@gmail.com> (Kyle's message of "Tue, 9 Aug 2016 06:02:48 -0400")
Kyle <kyle4jesus@gmail.com> 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
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Chris Brannon
` Zachary Kline
` Chris Brannon
` Kyle
` Chris Brannon [this message]
` Mike Ray
` Jude DaShiell
` Chris Brannon
` covici
` Zachary Kline
` covici
` Kirk Reiser
` Jason White
` Chris Brannon
` Jude DaShiell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpjqcipf.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=speakup@linux-speakup.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).