Re: [orca-list] My Fedora 22 Blues



Kendell:

You've made my day, my week, and my month!  Thank you!

kendell clark writes:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

hi
Something's weird with your system. I've never seen this before. It
looks like you're running two separate instances of gnome. One running
under wayland, and one running under x. Gnome is supposed to run on
the same tty as gdm, which is normally tty1. You can, of course, start
another instance on another tty if you want, but I don't have any idea
how to get to tty 25 to start one, and I'm not at all sure how one got
started there.
Btw, I fixed your name in espeak, so it should be in the next espeak
release.
Thanks
Kendell clark


Janina Sajka wrote:
Hi, Joanie:

You're correct. I think I wasn't groking what you were saying when
first I read your email.

Is this normal? To have gdm continue live in one tty, while Orca
and the desktop merrily run along in another tty? If so, that's new
to me. Fedora 21 didn't behave that way for me, nor any previous
Fedora.

Is it configurable as far afayk? I can't see how it adds value, at
least not to me.

Janina


Joanmarie Diggs writes:
Hi Janina.

When I return from the console to tty 1, I get a gdm screen.
Usually I have speech, but if speech-dispatcher is not speaking,
toggling Orca off and on again with Super+Alt+S solves it. I'll
add that to my to-look-into list. In the meantime, after I log
back in, the Orca I left running in my user session resumes
speaking. Is there any chance you're in gdm but didn't realize it
due to lack of speech?

--joanie

On 06/05/2015 07:11 PM, Janina Sajka wrote:
I appreciate all the thoughts conveyed to my problem. But, I
think what's actually happening on my system has become muddled
in the process.

I have no problem with Speakup, or with moving among the 23
open consoles I have running Speakup.

The problem is Orca and Speech-Dispatcher -- or something in
the GUI. Once I leave tty1 where the GUI is, I can run Speakup
all day, changing consoles as much as I might want. But, when I
return to tty 1, there's no response whatsoever. Orca doesn't
speak, and as far as I can tell, nothing else is responding in
any way.

For instance, I cannot do:

Alt F2

aplay ~/myfile.wav

Not even if I add something like "-D plughw:4" to the above
command. Yes, I have multiple audio devices.

Which leads me to a thought. I suppose I should try putting 
Speech-Dispatcher on a completely separate device. I haven't
need that since using my ICE17724 device, but I suppose this
would be worth a try.

Janina

kendell clark writes: hi I seriously doubt fedora would do
anything like that deliberately. If they had, there would be a
change log entry. Pulse is a problem for speakup, no doubt
about it, but otherwise usually just works. This is really a
speakup problem and needs to be fixed by the speakup devs, 
because pulse audio isn't going away. Now that I've said all
that, I don't know  how to solve the problem reliably. If you
can get into the gui, make sure speakup is running, and then
run sudo espeakup, while in the gui. After that, speakup should
work as normal. It's something to do with pulseaudio and
speakup conflicting with each other. Just as an aside,
speech-dispatcher's alsa support really leaves something to be
desired. It frequently crashes when using espeak Thanks Kendell
clark


Janina Sajka wrote:
I have pulse disabled the usual way I've been disabling
it ever since Redhat foisted pulse on us.

/usr/bin/pulseaudio is a 0-byte file chmod 444 owned by
root:root.

Speech-Dispatcher has been told to use alsa.

PS: I actually suspect something explicitly Fedora. I'm
suspicious there's some new setting designed to keep
newbies locked onto the gui, lest they stray into console
land and freak out. That kind of quote unquote feature
wouldn't surprise me. I guess I should troll the change
log.

Janina

Jason White writes:
covici ccs covici com <covici ccs covici com> wrote:
I bet it has something to do with pulse audio -- do
you have a hardware synth to use with speakup to
check?

It's also worth noting that I can't reproduce any of
these issues under Arch Linux with Pulseaudio, GNOME
and Orca installed. It's something Fedora-specific,
apparently.

_______________________________________________
orca-list mailing list orca-list gnome org 
https://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information
on Orca. The manual is at 
http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.
html




The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
Log bugs and feature requests at
http://bugzilla.gnome.org Find out how to help at
http://live.gnome.org/Orca/HowCanIHelp



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJVc50eAAoJEGYgJ5/kqBTdFZkP/3TPuPa14ZSIul3/zsmbXxCO
YmELrLSqhnlcx77PREjkpPpzEhqVBGSuH78WbnlHF3lNAJ1IcjuTnn3SUqk25jWS
yAkAa9nhhUYivgkiVGGdOBxkn9uj+YCWvbgIbYmnc5H8Ccke+nap8ByZ4/L6zhym
AZm3xsLMyXzqjakk/CSNYPlKnRCBFRZJEaVvFLqarWrUCI16idbIKH+ji//b5CAE
cQ40wXbSE5L93VytVzppi+gQ5A4xzKwqNYnokuDDZdg8DadLfK3zFuSYlgLtY2sK
XXXS2CNyKAOVUr+meqyaGitILM+IOahqBSSXEO8o8BWjsA/SDdx06ZB9gFMLtqEv
Ek3IOIoSFZYTK1WXLxm8ePgF3OvVrxwKz1yxCR+lIyOyo0ZfuvjjRDbGT7YEntrz
6YaZe0ZxGxbv8xqprn5QQ5a89LZjz9jZmTBODqG/w8A4v1HRGOfIEsbHrqtRhL9k
voBbSU2R0erVd2PWHEvH6FDg/lNC42XQFFjXWwenpUqtX9sBnNmK0saZbFzXJUfa
0K1jJ7gd/qAmVNGXA0SeajppjwdVfFcJ2+jjEJEMTl1OMzvxQXKaou+yrTHMGuBb
Z76ZOFN1mXgSQVRdUSU2fDAsSuvUTrKtVQG5iDdDLKPscGuOqbUUXxG7WY3c8pGR
+JH3pKvUApNlIYJGdpfo
=PrJj
-----END PGP SIGNATURE-----

-- 

Janina Sajka,   Phone:  +1.443.300.2200
                        sip:janina asterisk rednote net
                Email:  janina rednote net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:       http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,  Protocols & Formats     http://www.w3.org/wai/pf



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]