From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from imr-m07.mx.aol.com (imr-m07.mx.aol.com [64.12.138.209]) by speech.braille.uwo.ca (Postfix) with ESMTP id BF0C0109B1 for ; Tue, 2 Jun 2009 19:56:51 -0400 (EDT) Received: from imo-da03.mx.aol.com (imo-da03.mx.aol.com [205.188.169.201]) by imr-m07.mx.aol.com (v107.10) with ESMTP id RELAYIN2-34a25bc3e278; Tue, 02 Jun 2009 19:56:46 -0400 Received: from mwhapples@aim.com by imo-da03.mx.aol.com (mail_out_v40_r1.5.) id f.bd2.42840ff5 (37252) for ; Tue, 2 Jun 2009 19:56:43 -0400 (EDT) Received: from [192.168.1.66] (mwhapples.plus.com [80.229.137.216]) by cia-ma07.mx.aol.com (v123.4) with ESMTP id MAILCIAMA072-91844a25bc33101; Tue, 02 Jun 2009 19:56:42 -0400 Message-ID: <4A25BC31.2050500@aim.com> Date: Wed, 03 Jun 2009 00:56:33 +0100 From: Michael Whapples User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1pre) Gecko/20090601 Shredder/3.0b3pre MIME-Version: 1.0 To: "Speakup is a screen review system for Linux." Subject: speakup 3.0.4 and the timeout issue Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AOL-IP: 205.188.169.201 X-Mailer: Unknown (No Version) X-Spam-Flag: NO X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.12 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 23:56:52 -0000 Hello, I remember seeing a comment that speakup 3.0.4 fixed the problem of slow response to certain review keys and that it was thought that fix also fixed the timeout issue which causes speakup to deactivate. I just tried my system on the start up (which seems to be a reliable way to cause the problem) and it happened. I have speakup as modules and pressed numpad enter to silence speech and didn't touch a key until booting finished and when I tried to use a screen review key I found speakup didn't talk. Looking at dmesg I found the message saying about too many timeouts. If it would be useful I have the output from dmesg (command issued was "dmesg >/dmesg.output"). Should I do anythig to get more detailed output for you? Michael Whapples