Re: espeakup stops speaking bookworm arm64

[Chevelle <cstrobel@crosslink.net>]

    I have the AMD64 build of bookworm, but I have had it stop 
speaking.  Sometimes if I have a graphical session running, then switch 
to a speakup console, it is very slow to respond.  I wrote a simple bash 
script like this:

#!/usr/bin/bash

sleep 5

ls


I start that in the terminal with ORCA running then switch consoles to 
another session.  With that I can get some errors in the 'espeakup' 
debug log like this:

error: Device or resource busy
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
error: Device or resource busy
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
error: Device or resource busy
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
error: Device or resource busy

Also if it is talking and you type something in the console you are in, 
it can't stop the speech.  Maybe I'm expecting to much, I'm not sure how 
it is designed to work.

Not sure if that helps.


On 8/18/23 12:39, Frank Carmickle wrote:
> Greetings,
>
> I've been living with this for the last sixish months, and it's annoying. I have a console where I can just up arrow and hit enter for
>
> `killall -1 espeakup`
>
> I would love to see this get fixed but I've gotten nowhere with debugging it.
>
> I haven't tried Sam's recommendation of having a middle layer of pulseaudio or pipewire to keep the audio buffer always full with silence when it's not speaking. I spent so much time trying to get a working machine before, that I've not wanted to go back to work on it again for a bit. I'll probably get to it when the kids go back to school in a few weeks time.
>
> I'll let you know if I find it to be of help.
>
> --FC
>
> > On Aug 17, 2023, at 13:48, Geoff Shang <geoff@QuiteLikely.com> wrote:
> >
> > Hello,
> >
> > I just updated to Bookworm on my work VM running under VMWare 17 under Windows 11 and am experiencing the same problem.
> >
> > This was not happening under Bullseye.
> >
> > The only other thing that I can add to what has already been described in this thread is that using conventional Debian methods to stop the espeakup process takes a long time.  Running espeakup in debug mode doesn't print anything to the console, and when I lose speech, I have to press control-backslash to kill it (control-c doesn't work).
> >
> > I've only just seen the suggestion to test with the debug versions, which I will try at some point soon.
> >
> > I'm running just in the console, no desktop environments.
> >
> > BTW: I was just proofing this message and it died.  I was cursoring down through this email, so I wasn't reviewing by character this time.
> >
> > Cheers,
> > Geoff.