public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Michael Whapples <mikster4@msn.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speech Dispatcher bugfixes, request for help with testing
Date: Mon, 04 Jun 2007 11:36:48 +0100	[thread overview]
Message-ID: <BAY103-DAV15053CD74D19E360EB3A808E210@phx.gbl> (raw)
Message-ID: <1180953408.8377.10.camel@layla> (raw)
In-Reply-To: <1180889365.23463.27.camel@labts16.troja.mff.cuni.cz>

Hello,
I don't know if this is known about and whether it is part of the
problem with occasional crashes of speech-dispatcher, but I have found
once speech-dispatcher was crashing on me fairly soon after the initial
start (seemed to be the initial start after booting only, not when it
was started again after that first crash), and when I turned debugging
in speechd.conf to 5 and viewed the log file, it seemed to be that the
espeak generic module had returned wrong number of bytes (unfortunately
I had not set debugging in espeak-generic.conf). That was using
speech-dispatcher 0.6.1, and I haven't noticed this since moving to
0.6.2, was this problem solved, or could it still be a potential
problem? I ask this as (typically) when I set debugging on (using
0.6.1), it took some time before I actually got a crash.

From
Michael Whapples
On Sun, 2007-06-03 at 18:49 +0200, Hynek Hanke wrote:
> >sorry to say that I experienced a crash of SD again. It doesn't happen
> >very often - every 2 or 3 days - but it still does happen.
> > /var/log/speech-dispatcher/speech-dispatcher.log
> > only tells that the connection was closed.
> 
> Hello Hermann,
> 
> could you please send me the logfile with the crash? You will first need
> to set LogLevel to 5 in /etc/speech-dispatcher/speechd.conf . Are you
> sure it is a crash of SD and not SpeechD-Up? Is the process
> speech-dispatcher still running after that?
> 
> Have a nice day,
> Hynek
> 
> 
> 
> 




  parent reply	other threads:[~ UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Hynek Hanke
 ` Hermann
   ` Jan Buchal
     ` Hynek Hanke
       ` Hermann
         ` Hynek Hanke
           ` Hermann
             ` Hynek Hanke
     [not found] ` <1180953408.8377.10.camel@layla>
   ` Michael Whapples [this message]
  -- strict thread matches above, loose matches on Subject: below --
 hanke
 ` Hermann
   ` hanke
     ` hermann
     ` Hermann
       ` Jan Buchal
         ` Hermann
           ` Jan Buchal
             ` Hermann

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=BAY103-DAV15053CD74D19E360EB3A808E210@phx.gbl \
    --to=mikster4@msn.com \
    --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).