From: "Rob Hudson" <captinlogic@gmail.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: trying again, new talking arch and audio problems
Date: Wed, 14 Aug 2013 15:09:27 -0500 [thread overview]
Message-ID: <D1CD361FD14D420CB36FA87C1C3FF606@train> (raw)
In-Reply-To: <520B8F51.6050403@gmail.com>
I hear nothing. NO espeak. I still find it weird that sound works otherwise.
----- Original Message -----
From: "Kyle" <kyle4jesus@gmail.com>
To: <speakup@linux-speakup.org>
Sent: Wednesday, August 14, 2013 9:08 AM
Subject: Re: trying again, new talking arch and audio problems
> When typing
>
> espeak hello
>
> Do you hear "hello" at all, or do you only get the errors? For some
> reason, Espeak will many times produce a whole host of strange-looking
> alsa errors, but it still talks. This especially causes problems in
> Debian Wheezy if you have installed a desktop environment, as Espeak
> speaks all the errors that are printed to the console as GDM begins
> running, so the user is forced to go into a text console to stop it
> prior to logging into GDM. However, on a Talking Arch system, the errors
> can generally be safely ignored, as long as Espeak is in fact talking.
> Most of the time, the espeakup system service will log the harmless
> errors rather than printing all that chatter to the console. If the
> harmless errors I refer to are in fact not harmless, e.g. Espeak simply
> doesn't talk, please write back, and I will dig a bit deeper into the
> problem if I can. Hope this helps.
> ~Kyle
> http://kyle.tk/
> --
> "Kyle? ... She calls her cake, Kyle?"
> Out of This World, season 2 episode 21 - "The Amazing Evie"
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Rob Hudson
` Kyle
` Rob Hudson [this message]
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=D1CD361FD14D420CB36FA87C1C3FF606@train \
--to=captinlogic@gmail.com \
--cc=speakup@linux-speakup.org \
/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).