From: Chris Brannon <chris@the-brannons.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: LIBASOUND_THREAD_SAFE workaround and ArchLinux
Date: Sat, 13 Aug 2016 14:31:19 -0700 [thread overview]
Message-ID: <87ziogbbko.fsf@mushroom.localdomain> (raw)
In-Reply-To: <3CFDD33E-4FE6-4667-BF1F-48AC7E40D402@speedpost.net> (Zachary Kline's message of "Sat, 13 Aug 2016 10:39:09 -0700")
Zachary Kline <zkline@speedpost.net> writes:
> Hi All,
>
> Does anybody have a way of implementing the LIBASOUND_THREAD_SAFE=0
> workaround in Arch, with its espeakup.service systemd unit?
Hi Zack and all,
You've got a couple of options now.
Samuel Thibault sent a patch to the Debian Accessibility list to fix the
issue in libasound. I've been running with that patch over here, and
espeakup seems to be working fine.
I put that patch up on my server so everyone can get it easily:
http://the-brannons.com/asound.patch
On Arch, you can add that patch to your ABS tree, adjust the PKGBUILD,
and rebuild alsa-lib from source.
If you'd rather use the environment variable workaround discussed
earlier, I think the following steps should work for you under systemd.
Copy /usr/lib/systemd/system/espeakup.service to /etc/systemd/system.
Edit /etc/systemd/system/espeakup.service.
Find the line that says [Service].
After that line, insert
Environment=LIBASOUND_THREAD_SAFE=0
-- Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Mark Peveto
` Chris Brannon [this message]
` Zachary Kline
` Chris Brannon
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=87ziogbbko.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).