From: Don Raikes <don.raikes@oracle.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: RE: Latest Chapter in the Quest for Orca
Date: Mon, 3 Jun 2013 09:10:56 -0700 (PDT) [thread overview]
Message-ID: <d64d3e09-cbba-4888-ae44-3171bc8f3b25@default> (raw)
In-Reply-To: <20130603105822.6E7202298F@server1.shellworld.net>
I can tell you from my experience with backtrack, that if you login to the console with Speakup working, then turn Speakup off using keypad insert+keypad plus then run startx, that gnome came up talking just fine. I did not have speech-dispatcher or pulseaudio running on the backtrack livecd when I experienced this situation.
-----Original Message-----
From: Martin G. McCormick [mailto:martin@server1.shellworld.net]
Sent: Monday, June 03, 2013 3:58 AM
To: Speakup is a screen review system for Linux.
Subject: Re: Latest Chapter in the Quest for Orca
Jason White writes:
> What happens if you log in from the console and then run startx to
> commence a Gnome session?
What you get when the system boots precludes much control other than through an X console. You hear the speakup kernel starting up and complaining about many things such as the state of the alsa configuration. Apparently, this is okay as sound and sound effects do run. Eventually, X starts on its own and you loose the ability to stop speakup.
Speakup continues to complain about many things and then describes everything starting up until about where bluetooth starts at which point it stops talking.
What should happen after that based on a few tantalizing events is that you get the orca login window but nothing has worked after that.
If you log in from a ssh console and tell the system to reboot, speakup begins talking again to announce the shutdown and does so for a couple of seconds until it dies as all the running processes are killed off.
From what I can tell, X takes over automatically and stays on until you log in from somewhere else and kill gdm3 at which time you can get all your speakup consoles back or you reboot or halt the system at which time speakup sings it swan's song so to speak as the system goes down.
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Martin G. McCormick
` Don Raikes [this message]
` Jason White
-- strict thread matches above, loose matches on Subject: below --
Martin G. McCormick
Martin G. McCormick
Martin G. McCormick
` Jason White
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=d64d3e09-cbba-4888-ae44-3171bc8f3b25@default \
--to=don.raikes@oracle.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).