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: System still locks up on me in Debian
Date: Thu, 1 Jan 2009 11:35:35 +0900	[thread overview]
Message-ID: <5C4D2C5F4EB64E5EA82C36EADD16BFEF@bouncy> (raw)
In-Reply-To: <20081231190813.GA16254@clearwire.net>

Probably nothing.
Once the doubletalk buffer fills up, the doubletalk will handshake off and 
leave speakup stuck.
I used to get around this by powering the doubletalk off and on to empty the 
buffer.
This is a known bug. Once you had too much text the whole thing can lock 
solid.
I have no idea if anyone is looking into this bug; most people don't have 
speakup compiled into the kernel these days and just either load as modules 
and turn speech off or silence at bootup which is not ideal.

Not sure if this is beeing worked on at all and who would debug it.

Regards, Kerry.

----- Original Message ----- 
From: "Gaijin" <gaijin@clearwire.net>
To: "SpeakUP Mailing List" <speakup@braille.uwo.ca>
Sent: Thursday, January 01, 2009 4:08 AM
Subject: System still locks up on me in Debian


> Hello all,
>
> Just writing to report that the latest speakup upgrade in debian
> is still crashing when performing long displays of text while using the
> LTLK module.  I'm running things with the 2.6.26-686 kernel on a celeron
> system.  Usually I just hit keypad enter to silence the boot messages,
> but if I don't do that, then the system locks up tight, requiring  a
> press of the reset switch or a full power-off.  Any ideas on what I may
> be doing wrong?
>
> Michael
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 


  parent reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gaijin
 ` Nick Stockton
 ` Kerry Hoath [this message]
   ` Nick Stockton

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=5C4D2C5F4EB64E5EA82C36EADD16BFEF@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).