Hello,

if the output of following command:
cat /sys/accessibility/speakup/no_interrupt
is just: 1
try this:
echo 0 > /sys/accessibility/speakup/no_interrupt

Best,

Didier

On 20/05/2019 19:47, Terry D. Cudney wrote:
> Hello,
> 
>     Yes, I have tried all key possibilities to interrupt speech, to no avail.
> 
>     Initially, I was using a standard 104-key ps-2 keyboard, but I have tried 
> a 104-key USB-connected keyboard and more recently on my Asus laptop withthe 
> integrated keyboard. The results are the same, no matter which keyboard was 
> being used.
> 
>     I might add, that these computer/keyboard combinations have worked 
> flawlessly with previous versions of the debian installer, running-debian and 
> with raspian on the Pie.
> 
>     The problem is only with more recent versions of speakup/espeakup, in the 
> debian installer and raspian. I don't know about speakup/espeakup in other 
> distributions.
> 
>     As I described in a previous post, I did the complete installation of 
> raspian on the pie (the installer is not needed there) and the behaviour 
> where key presses do not interrupt speakup/espeakup is the same. as 
> experienced in the debian installer.
> 
>     On a side note, I have spoken with Kirk Reiser, one of the original 
> developers of speakup. He informed me that this behaviour began at leat 1.5 
> years ago. Kirk's experience is similar, but a bit different to mine. On his 
> machine speakup does respond to key presses, but the response is only after 
> an unacceptable delay. He, as a workaround, replaces the /usr/bin/espeakup 
> installed by the current debian release, with a copy of the /usr/bin/espeakup 
> from an older release. Doing this, speakup responds to keyboard input 
> immediately.
> 
>     From these observations it would seem that there was some change made  to 
> the espeakup code 1.5-2 years ago that produces this unacceptable lag in, or 
> lack of, response to key presses.
> 
>     Samuel, can you ascertain what changed in the espeakup  code about 1.5 to 
> 2 years ago, that could cause this?
> 
>     Thanks,
> 
>     --terry
>     
> 
> 
> 
> On Mon, May 20, 2019 at 08:23:01AM +0200, Samuel Thibault wrote:
> --> Samuel Thibault, le lun. 20 mai 2019 08:20:26 +0200, a ecrit:
> --> > Terry D. Cudney, le dim. 19 mai 2019 19:38:17 -0400, a ecrit:
> --> > >       Any observations/workarounds/solutions out there?
> --> > 
> --> > As Didier asked: which keys do you use to try to interrupt speech?
> --> 
> --> Ok, in another mail you answered, I then guess you tried all kinds of
> --> keys.
> --> 
> --> > Which kind of keyboard are you using, connected which way?
> --> 
> --> This, however, could be important to answer.
> --> 
> --> Samuel
> 

Reply via email to