public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Jacob Schmude <jschmude@adelphia.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: my DTK-generic log file
Date: Sat, 1 May 2004 22:15:27 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0405012211010.2388@beavis.screwball> (raw)
In-Reply-To: <Pine.LNX.4.58.0405011736510.18935@maranatha.charter.net>

Hi
Are you starting speech dispatcher in an init script before you log in as
root? If so, this creates a problem with the dtk-generic module. I've not
yet been able to track it down, and am not sure whether it's a problem
with just the dectalk generic module or all modules that utilize the
generic module. However, starting it before you log in causes the no
speech output problem. I know it's not a problem with speech dispatcher
itself, since flite will work fine when started in an init script. Haven't
tried festival this way.
Other than that, I can't think of anything else at the moment. If that's
not it, I'll have to rack my brains some more.

On Sat, 1 May 2004, Cheryl Homiak wrote:

> Looks a lot like mine, except that your config file is still set to call
> dtk-say. Has your executable actually been renamed to that; I guess that
> was the case in older versions/
>
>
> --
> Cheryl
> "Where your treasure is, there will your heart be also."
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>


  parent reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Stephen Clower
 ` Cheryl Homiak
   ` Stephen Clower
   ` dtk-generic working now Cheryl Homiak
     ` Jacob Schmude
       ` Shaun Oliver
         ` Cheryl Homiak
           ` Shaun Oliver
             ` Cheryl Homiak
   ` Jacob Schmude [this message]
     ` my DTK-generic log file Cheryl Homiak

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=Pine.LNX.4.58.0405012211010.2388@beavis.screwball \
    --to=jschmude@adelphia.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).