Well after thinking about it and messing with things a bit, I see now that the speechd.sh file in /etc/profile.d gets its execute flag turned off when the speechd daemon is stopped by running '/etc/rc.d/speechd stop'. So it should not be setting that environment variable in the future as long as you don't startup speech-dispatcher with the rc.d script. Look in /etc/speech-dispatcher/speechd.conf at the bottom line; it should say something like DisableAutoSpawn; Just stick a # sign in front of that and then save the file. This will probably get copied down to your $HOME directory if it hasn't already. On Thu, Feb 24, 2011 at 09:40:06PM -0700, Steve Holmes wrote: > I have to think about this a moment. If you are going to use > autospawn and run as individual user, then you should not start > speechd up as a system service. The autospawn deal will start it for > you and then it should not pull in the environment variable > declaration or care about it. I need to check that part out and see > if going back to user mode would cause a conflict with that > environment variable. That will give me something to play with after > I get pulse going here. So far, I have pulse going for playing media > files from the console. I'm a bit chicken to restart ALSA just yet > because I don't wanna lose speakup with espeak. Since ALSA is > configured now to use pulse, I might get away with not changing or > recompiling espeak yet. If it weren't for the threat of losing speech > and thus access to my system, I would be a bit more brave here. At > least I can ssh into this box from my laptop if I break speech, I > guess. > > On Thu, Feb 24, 2011 at 07:14:44PM -0500, Christopher Moore wrote: > > When I set speechd as a system-wide service, it put an export > > SPEECHD_ADDRESS = /var/run/... > > in a file under /etc/profile.d. When I went back to running speechd as > > a user, this line was not removed. Commenting it out seems to have > > solved the problem. > > > > Chris > > On Thu, Feb 24, 2011 at > > 01:28:37PM -0700, Steve Holmes wrote: > > > Assuming you want to continue using speech-dispatcher as a system wide > > > service, be sure you have started speech-dispatcher. Add /speechd to > > > your DAEMONS array in /etc/rc.conf or at least run thd daemon by hand > > > by typing, > > > /etc/rc.d/speechd start > > > to get it going for now. Then see how things go. If you would rather > > > use it as a user based deal, then edit > > > /etc/speech-dispatcher/speechd.conf and uncomment the AutoSpawn line > > > at the bottom of the file. In that situation, you would not need to > > > have the speechd daemon running at all. > > > > > > Note, this is for Arch Linux users. > > > > > > On Thu, Feb 24, 2011 at 12:49:42PM +0100, Hynek Hanke wrote: > > > > On 23.2.2011 01:18, Christopher Moore wrote: > > > > >It seems that spd-say thinks that speechd is a system-wide service > > > > > rather than a local service. > > > > > > > > Right. > > > > > > > > >application configuration or the value of the SPEECHD_ADDRESS environment variable. > > > > > > > > It says where it is taking the information from. Since spd-say has > > > > no application configuration, then you must have set the SPEECHD_ADDRESS > > > > variable. > > > > > > > > Try: > > > > env SPEECHD_ADDRESS > > > > > > > > Best regards, > > > > Hynek Hanke > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup at braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > _______________________________________________ > > > Speakup mailing list > > > Speakup at braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
