From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: help with espeak?
Date: Sat, 30 Sep 2006 09:51:31 -0700 [thread overview]
Message-ID: <20060930165131.GA8855@localhost.localdomain> (raw)
In-Reply-To: <7.0.1.0.0.20060930103344.02622b10@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Check the permissions and owner/group on espeak-data, and the files
that are in there. I found that under Debian at least, the permissions
and owner/group that the espeak distribution has set by default were
what was causing espeak not to speak for me. I found that setting the
espeak-data directory permissions to 755, and the permissions of the
files under espeak-data to 644 was what worked for me. I also have
both the directory and the files in it set to owner root, and group
root. Finally, the permissions on the speak binary are also set to
755, and the owner/group are root as well.
This is on a stand-alone system, which only I use, and which isn't
hooked up to my network frequently, which is separate from the outside
world anyway, so the above setup doesn't bother me in terms of any
possible security wholes in the slightest.
Also, make sure that speak is in the path. If you're using it via
speech-dispatcher, instead of just having speak in
espeak-generic.conf, you want to supply the full path,
(I.E. /usr/local/bin/speak in my case).
If espeak still doesn't work, especially by itself without
speech-dispatcher, then given that you had problems you said with
another speech engine failing to speak, I'd get your soundcard/speaker
issue resolved first, before moving forward, since that would seem to
be the main problem here in that case.
Greg
On Sat, Sep 30, 2006 at 10:34:49AM -0600, TheCreator wrote:
> Hello list,
> I'm trying to run espeak. I moved the data dir to /usr/share, and
> when I run it, I don't get any errors, but its not giving me any sound.
> Any ideas?
> Thanks,
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFHqCT7s9z/XlyUyARAsoPAJ4mOuAz/po1ZyicWu2Wzbk6dl6LmACeNCMZ
5YaNeU2MFObFmFdnekbRlcY=
=st4B
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
TheCreator
` Gregory Nowak [this message]
` TheCreator
` Gregory Nowak
` TheCreator
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=20060930165131.GA8855@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).