From: "Adam Myrow" <myrowa@bellsouth.net>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: Stopping Speakup while using Gnome.
Date: Sat, 21 Apr 2007 19:11:40 -0500 [thread overview]
Message-ID: <000301c78472$cd7fa020$6101a8c0@dell> (raw)
In-Reply-To: <1177179905.23165.10.camel@localhost.localdomain>
You have to kill Speakup after you start Gnome. The reason is that when X
starts, it allocates itself a new virtual terminal. The commands to kill
Speakup only effect the virtual console that they are run from. Let's say
you are on tty1, which is the case when you first log in. When X starts, it
will turn TTY1 into a console for error messages and debugging output. X
will get the first free TTY. Using Slackware as an example, this will be
TTY7 since Slackware allocates 6 TTYs by default at boot time assuming you
are in run level 3. Thus, the command to kill Speakup should be given once
Gnome is up and running. HTH.
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Darragh
Sent: Saturday, April 21, 2007 1:25 PM
To: speakup
Subject: Stopping Speakup while using Gnome.
Hello,
How can I stop speakup listening for key presses when I'm in gnome?
I've tried pressing the ... I think it's the scrole lock. I cant remember
the name of the button. sorry. it's late. it's the third button in from the
top row on the right. that says you killed speakup. then I press insert and
enter and it says you turned me off but when I'm in gnome and I'm using orca
keystrokes speakup starts talking again. I don't want to unlode speakup
from memory as I often go back to a console to continue working on other
things so I would really like to know how to just temporarily stop it.
Or maybe I do need to completely unlode the module. but, how do I do this
without needing a reboot to get it working again? using modprobe
speakup_apollo doesn't work after using the command rmmod.
now, I may have that rmmod command wrong. It's been some time since I used
it and as I said, it's late and I'm probably not thinking as clarly as
usual.
Thanks in advance.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Darragh
` Adam Myrow [this message]
` Zachary Kline
` Darragh
` Janina Sajka
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='000301c78472$cd7fa020$6101a8c0@dell' \
--to=myrowa@bellsouth.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).