[orca-list] BEWARE: Fedora 15 & 16 Unusable for the Speech Dependent Orca User

[Janina Sajka]

Jason White writes:
> Have you tried configuring speech-dispatcher to use a network socket rather
> than a UNIX socket, e.g., 127.0.0.1? That might give you a work-around until
> the real issue is fixed.
> 
Good idea. Turns out this is fairly simple. In my
/etc/speech-dispatcher/speechd.conf, I do:

 CommunicationMethod "inet_socket"


I believe the following two are default, but just in case, I uncomment
them as well:
 Port 6560
 LocalhostAccessOnly 1

 Now, I'm somewhat concerned that 'nmap -P0 localhost' doesn't show port
 6560. Nevertheless, I try my spd-say command after rebooting ...

> Also, speech-dispatcher should report the error if it can't access the socket;
> it shouldn't hang, in which case there's a bug pertinent to the lack of error
> checking in addition to whatever the underlying problem is.
> 
Indeed, there seems such a bug as hang is what it did. But, now I get
errors as follows. I don't know where to take this. Advice much
appreciated.

janina at sonata 19:02:08 ~$spd-say hello 2>&1
Failed to connect to Speech Dispatcher:
Error: Can't connect to unix socket /home/janina/.speech-dispatcher/speechd.sock: Connection refused. Autospawn: Autospawn failed. Speech Dispatcher refused to start with error code, stating this as a reason: Error: can't open logging file /var/log/speech-dispatcher//speechd.log! Using stdout.
 Thu Oct 27 19:02:22 2011 [184686] ALSA ERROR: Cannot open audio device plughw:2,0 (Device or resource busy)
 Thu Oct 27 19:02:22 2011 [184717] ALSA ERROR: Cannot initialize Alsa device 'plughw:2,0': Can't open.
festival_client: connect to server failed
Error: can't open logging file /var/log/speech-dispatcher//speechd.log! Using stdout.
Autospawn failed: Mismatch in communication methods. Client requests unix_socket, most probably due to its configuration or the
value of the SPEECHD_ADDRESS environment variable, but the server is configured to provide the inet_socket method.

How so still looking for unix sockets? And how so can't write a log? 


Checking the log directory is owned by root, gid root. Directory is set
700, and file is 660. Seems root should be able to write. Or, is SD not
running as root?

Janina

-- 

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

Chair, Open Accessibility	janina at a11y.org	
Linux Foundation		http://a11y.org

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