From: "Keith Hinton" <keithint38@CommSpeed.net>
To: <speakup@braille.uwo.ca>
Subject: Regarding Speech-Dispatcher, Speechd-up, and ESpeak with Speakup.
Date: Sat, 17 Feb 2007 14:24:14 -0700 [thread overview]
Message-ID: <000c01c752d9$f95e34b0$6401a8c0@YOUR3ADE1B78A3> (raw)
Hi List,
I'm more convinced then ever now that speechd-up is what is crashing. I have to keep typing "Speechd-up" to restore communication.
The question is: Why?
What exactly was that backtrace about?
Could a chron job be setup to monitor if speechd-up is running, and if it crashes or whatever, instantly reboot it the instant it crashes?
I need a temporary workaround, short of turning off keyboared echo in Speakup with ESpeak. This, as I have said is on AMD64 machines, spisifically. Speechd-up
does not crash on my Pentium box, no matter what I do, doesn't matter how fast I type with keyboared echo on, somehow it's able to keep running. On my
AMD Athlon server, however
it will crash after a period of time, wich I cannot define. It just will suddenly crash. As long as ESpeak is being used (Sinse it is so responsive compared
to a laggy Flite)
On my AMD that has one gig of RAM, it is severely responsive.
So quick, that I believe Speechd-up gets overwelmed with the generic module reloading, etc. So, Speechd-up chooses to crash. What do you all think about my question, suggestions?
Regards,
--Keith.
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton [this message]
` Hynek Hanke
` Ralph W. Reid
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='000c01c752d9$f95e34b0$6401a8c0@YOUR3ADE1B78A3' \
--to=keithint38@commspeed.net \
--cc=speakup@braille.uwo.ca \
/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).