From: "Marcel Oats" <moats@orcon.net.nz>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Speakup and Orca working together in wheezy, revisited?
Date: Thu, 12 Apr 2012 15:03:17 +1200 [thread overview]
Message-ID: <45909676B2A74FA1AB83F7983177ADD0@Audio1> (raw)
Hi folks, this might seem a bit repeditive, I would like to have a wheezy
system to play with, and have it already, but I am wanting to have it so as
speakup can run alongside Orca. I believe this is possible, but haven't
found any real info as to how to do it, though I have read that the file
/etc/pulseaudio can be edited, though this file does not exist. If I
install wheezy with speakup (running the installer with the s parameter)
this is fine, we have a system, gnome starts (as does speakup) and if you
want to stop speakup reading most messages you can go to the first tty with
ctrl+alt+f1. We can log in, and then decide to install the "gnome-orca"
package.
After that is where things become interesting: we can restart the system and
Orca will automatically (here anyway) read the logon screen, and we can log
on; but that is all we can do in gnome, any other commands such as alt+f1 to
open the menus, must produce some kind of error, and the only thing that is
usable, is, surprizingly enough, orca preferences. Now it would appear that
since speech dispatcher is being used by both speakup and orca? ? ? speakup
is now unable to talk, though commands in the CLI are exicuted, slowly.
I am wondering about two options here: since I can see me wanting to enable
and disable speakup at will, should I look at booting the installer and
having it accept ssh connections, going in there, and installing it from
another machine, loading orca etc (since it can provide a terminal anyway)
and if need be modprobing speakup_soft and running espeakup when needed
(though it could still cause problems)
Or,
asking how we allow both to run?
Sorry about the long winded questions.
Marcel
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Marcel Oats [this message]
Martin McCormick
` lutz kaiser
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=45909676B2A74FA1AB83F7983177ADD0@Audio1 \
--to=moats@orcon.net.nz \
--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).