Your message dated Thu, 21 Dec 2017 19:51:15 +0100
with message-id <32f9a3ba-5600-1050-ed14-e7e2d2f69...@debian.org>
and subject line Re: Bug#712629: Acknowledgement (espeak: fails to speak final
chunk)
has caused the Debian Bug report #712629,
regarding espeak: fails to speak final chunk
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
712629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: libespeak1
version: 1.43.03-2
tags: patch, upstream
severity: important
Hi. I noticed that espeak as an emacspeak speech server is basically
unusable if you're using pulse, which is kind of the default
configuration in wheezy.
This made my accessibility experience quite difficult.
You don't notice with orca because it looks like speech-dispatcher
handles its own audio. That's also kind of broken, but I'll file
another bug for that.
Attached is a patch that fixes the problem.
I'd really like to see this in a stable update and would be happy to
help with that process.
Also, this should be reported as an upstream bug.
pulse-trigger-on-final-chunk
Description: Binary data
--- End Message ---
--- Begin Message ---
On 17-12-17 21:37, Paul Gevers wrote:
> On Sun, 23 Jun 2013 11:43:57 -0400 Sam Hartman <hartm...@debian.org> wrote:
>> Well, it does look like the bug is fixed.
>
> So, should this bug been closed at the time?
Sam contacted me in private and confirmed that the issue can be closed
as it doesn't appear to be present in jessie, stretch or buster.
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
