Re: Accessibility frustrations

[Fernando Herrera <fherrera gmail com>]

Hi,

Yesterday I sent a patch to festival developers to _always_ trust
127.0.0.1 as localhost and it's now on their CVS, so it will appear in
festival 1.96.

Thanks

Salu2 

On 8/2/05, "Dorado Martínez, Francisco Javier" <FDMA once es> wrote:
> Hi,
> 
> I had the same problem some months ago.
> 
> On Festival 1.4.3 edit /usr/share/festival/festival.scm
> 
> And locate the server_access_list variable, it's has to be like this:
> 
> (set! server_access_list '("localhost\\.localdomain" "localhost"))
> 
> This will add localhost.localdomain hostname, you have to add whatever your
> hostname is and then restart festival's server.
> 
> Regards,
> 
> Javier.
> 
> 
> -----Mensaje original-----
> De: Fernando Herrera [mailto:fherrera gmail com]
> Enviado el: martes, 02 de agosto de 2005 3:53
> Para: Nolan J. Darilek
> CC: gnome-accessibility-list gnome org
> Asunto: Re: Accessibility frustrations
> 
> 
> Yes, I had the same problem than you. Festival 1.95 only allows connections
> from "localhost" as defined by its default configuration file, but the code
> checking this only gets the first entry for a hostname, so if you have
> something before localhost on your /etc/hosts file, it fails. I think this
> is a bug on festival, but gnome-speech festival backend should be more
> robust against this errors.
> 
> Salu2
> 
> On 8/2/05, Nolan J. Darilek <nolan thewordnerd info> wrote:
> > If this already exists then do let me know, but would it be possible
> > to have better logging in Gnopernicus and the various GNOME
> > accessibility components?
> >
> > Recently I had a situation where, after a fresh Ubuntu install,
> > Gnopernicus stopped working. I had no idea why. The logs were claiming
> > that speech was initialized, but nothing spoke. I don't think that
> > Debian or Ubuntu include the test binaries, so I snagged the latest
> > gnome-speech and tried building it . . .
> >
> > I'll save the long list of additional things I tried by skipping to
> > the end. I'd added my computer's hostname after localhost in
> > /etc/hosts to have it, not localhost, appear in my emacspeak window
> > title . . . and I think this may have somehow caused Festival to start
> > refusing connections, as the machine was no longer resolving to
> > localhost (or, it was, but my computer's hostname was actually
> > returned for lookups of 127.0.0.1.)
> >
> > I'll do more testing on this once I've gotten over the novelty of
> > having a working machine again. :) Are there logs other than my
> > .xsession-errors that might have helped me resolve this? Would it be
> > possible to add such facilities, even if it means proxying application
> > connections through some layer higher than festival to create the
> > context of a logging facility? (I.e. gnome-speech opens a TCP
> > connection and pipes all received data to whatever backend driver is
> > in play, so if it refuses a connection then the refusal is logged by
> > gnome-speech.) Or perhaps this is already possible? Admittedly, I'm
> > not very familiar with CORBA and GNOME's use of it.
> >
> > And, because I don't want to send another message for a (hopefully)
> > simple question . . . :) How can I have Gnopernicus work after sudo?
> > If, for instance, I want to run gksu, synaptic and friends, currently
> > any windows spawned after the sudo don't speak at all. I've enabled
> > GNOME accessibility for root, but this doesn't seem like it's enough.
> >
> > Thanks.
> > _______________________________________________
> > gnome-accessibility-list mailing list
> > gnome-accessibility-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> >
> >
> _______________________________________________
> gnome-accessibility-list mailing list gnome-accessibility-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> _______________________________________________
> gnome-accessibility-list mailing list
> gnome-accessibility-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> 
>