it's done speechd works in system-wide-mode in arch including gdm orca and console

[Trevor Saunders]

Hi,

On Mon, Oct 11, 2010 at 08:30:36AM -0700, Steve Holmes wrote:
> This is interesting that Orca is involved with specifying how speechd
> is launched.  As a packager, that concerns me greatly that one who
> installs speech-dispatcher would have to make modifications to orca.
> If we make a change to Orca for the Arch package of speechd, this
> would have an adverse impact on how Orca runs on other distros.  Could
> you elaborate as to which orca script you had to change? If it was the
> .desktop file, maybe I could add something to it to dynamically check
> for speechd running and then set environment accordingly.  We don't
> want to get into a situation where one package starts altering the
> contents of another - sounds like a bad idea to me.

as he said all he's modifying in orca is that he's setting
SPEECHD_ADDRESS, because  gdm doesn't seem to be sourcing /etc/profile.
I took a quick look and the gnome doc I found seemed to claim that the
gdm script that invokes the daemon does source /etc/profile.  However on
debian atleast there doesn't appear to be any such script, So I'm not
sure what you'll find.

> Oh, and another side effect I discovered over the weekend with
> specifying the environment variable SPEECHD_ADDRESS in any default
> basis is that autospawn wouldn't work until that variable were
> removed.  Again, I'm considering this as a packager.  If I set things
> up to run as a system wide service, it makes it harder for a user to
> choose session mode if they want. This bit of choosing between session
> or system mode is not going to be all that simple for an end user who
> installs the package without much more fiddling.

Well, what you can do is have a shell fragment in /etc/default/speechd
probably that sets is a system mode speechd runs and what address it
uses, then you can source that /etcprofile.d/speechd and that way
SPEECHD_ADDRESS  is only set if the system service is enabled.  This
doesn't help a user on a system where a system wide speechd is running
who still want's to run there own speechd, but it should take care of
most cases, and all that user needs to do is unset SPeeCHD_ADDRESS.

HTH
Trev

> 
> On Mon, Oct 11, 2010 at 04:43:10PM +0200, Halim Sahin wrote:
> > Hi,
> > The problem which was described by Steve was the fact that the
> > speechd_address couldn't be read from the gdm-user from /etc/profile.
> > I have first activated orca debug and found the traceback which shows
> > that speechd tried to autospawn because of missing adr of the running
> > speechd in system-mode.
> > 
> > I wasn't able to modify gdm to get the adr correctly so I added it in
> > the orca script itself.
> > 
> > Then I added a speechd user and started speechd with that uid.
> > su -s /bin/sh -c "speechd_cmd"
> > in speechd's init script.
> > 
> > Well it works as expected with only single specheed runing :-).
> > have a nice day.
> > 
> > 
> > _______________________________________________
> > Speechd mailing list
> > Speechd at lists.freebsoft.org
> > http://lists.freebsoft.org/mailman/listinfo/speechd
> 
> _______________________________________________
> Speechd mailing list
> Speechd at lists.freebsoft.org
> http://lists.freebsoft.org/mailman/listinfo/speechd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: 
<http://lists.freebsoft.org/pipermail/speechd/attachments/20101011/85914b8b/attachment.pgp>