public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Apollo stops talking from time to time
Date: Fri, 10 Apr 2009 20:37:46 +0800	[thread overview]
Message-ID: <1B2B67BF0CFF478DBE12CF3D2C097989@bouncy> (raw)
In-Reply-To: <49DF37BB.5080708@aim.com>

The apollo has a filthy implementation of handshaking.
I know that speakup has to try and work around this as much as it can, 
however this isn't perfect.
Sadly the best solution is to get a different speech synthesizer, however 
failing this provide as much information about the circumstances around the 
bug as you can.
I don't think apollos are that common these days.
Regards, Kerry.


----- Original Message ----- 
From: "Michael Whapples" <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, April 10, 2009 8:12 PM
Subject: Apollo stops talking from time to time


> Hello,
> I have noticed that my apollo seems to stop talking from time to time. The 
> last time this happened I looked at the output from dmesg and found a 
> message saying:
> Apollo: too many timeouts, deactivating speakup
>
> I am using GRML with speakup built from the source debian package Samuel 
> recently made. What's causing this and how might I solve it?
>
> Michael Whapples
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 


  parent reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Michael Whapples
 ` Samuel Thibault
   ` Michael Whapples
     ` William Hubbs
       ` Michael Whapples
 ` Kerry Hoath [this message]
   ` Michael Whapples

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=1B2B67BF0CFF478DBE12CF3D2C097989@bouncy \
    --to=kerry@gotss.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).