public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: nick G <nick6489@optonline.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: regarding speech-dispatcher, dectalk and the init script
Date: Sun, 02 May 2004 08:17:48 -0400	[thread overview]
Message-ID: <000601c4303f$7bbfd960$cc00a8c0@nickysp4> (raw)
In-Reply-To: <Pine.LNX.4.58.0405020659130.2572@beavis.screwball>

I think it's time for the maintainers of TuxTalk to work on it again.
Thanks,
Nick
----- Original Message ----- 
From: "Jacob Schmude" <jschmude@adelphia.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, May 02, 2004 7:02 AM
Subject: Re: regarding speech-dispatcher, dectalk and the init script


> Hi
> Speech-dispatcher executes as root in my rc.local script, and root most
> certainly has permission to access the say command. I get no output when
> running run_test either, nor when I try to use speechd-el with
> dtk-generic. Curiously, speechd-el can still use flite as its output even
> though dectalk won't work when started from the initscript.
> 
> On Sun, 2 May 2004, Hynek Hanke wrote:
> 
> > This is very strange.
> >
> > We should attempt to eliminate speechd-up from the possible places
> > where this problem might appear. Please can you repeat this proces (so
> > that dectalk wouldn't work with speechd-up) and try to run run_test
> > basic.test in src/tests after you login?
> 
> _______________________________________________
> 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
 Hynek Hanke
 ` Jacob Schmude
   ` Hynek Hanke
     ` Jacob Schmude
       ` Hynek Hanke
         ` Jacob Schmude
           ` Cheryl Homiak
       ` nick G [this message]
         ` dking
           ` Gregory Nowak
       ` Hynek Hanke

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='000601c4303f$7bbfd960$cc00a8c0@nickysp4' \
    --to=nick6489@optonline.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).