* LIBASOUND_THREAD_SAFE workaround and ArchLinux
@ Zachary Kline
` Mark Peveto
` Chris Brannon
0 siblings, 2 replies; 5+ messages in thread
From: Zachary Kline @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Hi All,
Does anybody have a way of implementing the LIBASOUND_THREAD_SAFE=0 workaround in Arch, with its espeakup.service systemd unit? I thought exporting the variable before starting the service would be enough, but it doesn’t seem to be passed into the environment properly.
It’s weird bugs like this which make me miss hardware synthesizers.
Thanks,
Zack.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: LIBASOUND_THREAD_SAFE workaround and ArchLinux
LIBASOUND_THREAD_SAFE workaround and ArchLinux Zachary Kline
@ ` Mark Peveto
` Chris Brannon
1 sibling, 0 replies; 5+ messages in thread
From: Mark Peveto @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Is it something that goes in pulseaudio's default.pa file?
Mark Peveto
Registered Linux user number 600552
Sent from sonar test box using alpine 2.20.14
On Sat, 13 Aug 2016, Zachary Kline wrote:
> Hi All,
>
> Does anybody have a way of implementing the LIBASOUND_THREAD_SAFE=0 workaround in Arch, with its espeakup.service systemd unit? I thought exporting the variable before starting the service would be enough, but it doesn’t seem to be passed into the environment properly.
>
> It’s weird bugs like this which make me miss hardware synthesizers.
> Thanks,
> Zack.
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: LIBASOUND_THREAD_SAFE workaround and ArchLinux
LIBASOUND_THREAD_SAFE workaround and ArchLinux Zachary Kline
` Mark Peveto
@ ` Chris Brannon
` Zachary Kline
` Chris Brannon
1 sibling, 2 replies; 5+ messages in thread
From: Chris Brannon @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: LIBASOUND_THREAD_SAFE workaround and ArchLinux
` Chris Brannon
@ ` Zachary Kline
` Chris Brannon
1 sibling, 0 replies; 5+ messages in thread
From: Zachary Kline @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Hi, Chris and All,
Thanks for this information. I ended up going for the environment method, although I used a drop in snippet instead of copying the whole unit. I hope a patch gets put upstream at some point soon, so this kind of sludge is not necessary.
Best,
Zack.
> On Aug 13, 2016, at 2:31 PM, Chris Brannon <chris@the-brannons.com> wrote:
>
> 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
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: LIBASOUND_THREAD_SAFE workaround and ArchLinux
` Chris Brannon
` Zachary Kline
@ ` Chris Brannon
1 sibling, 0 replies; 5+ messages in thread
From: Chris Brannon @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Chris Brannon <chris@the-brannons.com> writes:
> 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.
Oops, you probably don't want to use that patch after all.
For instance, if you run aplay with the patched library, it doesn't
terminate when it is done playing a file.
So for now, the only thing I know that will work is setting the
environment variable.
-- Chris
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
LIBASOUND_THREAD_SAFE workaround and ArchLinux Zachary Kline
` Mark Peveto
` Chris Brannon
` Zachary Kline
` Chris Brannon
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).