From: Hynek Hanke <hanke@brailcom.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup and software speech dying for no particular reason
Date: Thu, 28 Dec 2006 23:18:57 +0100 [thread overview]
Message-ID: <1167344337.3337.69.camel@chopin> (raw)
In-Reply-To: <001001c7264f$c4a68df0$6401a8c0@YOUR3ADE1B78A3>
Keith Hinton píše v Pá 22. 12. 2006 v 22:04 -0700:
> Sometimes, with software speech, I will be typing or whatever, and all of a sudden, (for no particular reason)
> that I can find, the speech will suddenly "die." So, I'll normally have to re-launch speechd-up.
> Either that, or sometimes re-launch speech-dispatcher.
That will most likely be due to a crash of some of the component. Could
you, please, after the situation happens, run
ps -a | grep speech
so that we can see whether speech-dispatcher and speechd-up is running
or not (and so where is the problem).
I understand this is difficult given you have no output from the
computer. But hopefully you will be able to run the command, then
restart speech and inspect the output later.
There is a known bug in the current distribution of Speech Dispatcher
which has been fixed in CVS. We will shortly be making a new bugfix
release. Maybe it is this problem.
> I'm using espeak as the software synthesizer, and I've seriously tweeked a few lines in spech-dispatcher, so that espeak is as responsive as ever.
> And, for the most part it works fine. What interests me is this speech-loss issue.
I'd be very interested in those changes. Maybe they could help other
users too.
With regards,
Hynek
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton
` Hynek Hanke [this message]
` Chris Norman
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=1167344337.3337.69.camel@chopin \
--to=hanke@brailcom.org \
--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).